How to archive merch content
asset taxonomy, naming conventions and retention policy so design files survive vendor changes
First steps — get oriented
This guide walks through asset taxonomy, naming conventions and retention policy so design files survive vendor changes as run on real Poland programs out of Warsaw. The first 24 hours matter most: gather the artefacts, identify the decision-makers, and confirm what is actually in scope versus what is assumption. Resist jumping to remedies before the problem is fully framed.
The operational playbook
Three concurrent workstreams keep the playbook on track. Stream 1 — Verification: validate the assumption, the timing constraint and the budget envelope on paper. Stream 2 — Stakeholders: notify procurement, finance and legal in parallel; do not serialise. Stream 3 — Backup options: identify two fallback paths before committing to the primary plan.
How to execute without slippage
Run a daily 15-minute standup for the first 5 working days; switch to twice-weekly thereafter. Document every decision in a single shared log — the audit trail matters when something goes sideways. Confirm IVA / VAT treatment in writing on day 1. For Poland, all production runs out of our Warsaw hub and ships nationwide with consolidated invoicing.
Poland-specific notes
VAT 23% is added via KSeF. Production runs out of our Warsaw hub with nationwide coverage across Poland. Vendor escalation and contingency activation are handled by your dedicated account lead — all correspondence is logged for procurement audit purposes.