Producer Launch Checklist: Entering a New Deposit Market Without the Scramble

Entering a deposit market is a product launch inside a payments system, and its critical path is the container's acceptance: scope determination, registration with the operator, recognition testing of physical samples, and marking approval - in that order, because pricing, artwork and logistics all depend on their outcomes. Around the critical path run the commercial workstreams: deposit and fee modelling into the price architecture, till and invoice configuration (deposit as a line, refunds as flows), distribution and retail communication, reporting integration, and the launch-stock plan that keeps pre-system inventory from stranding at the changeover.

This checklist sequences the whole entry; timings are for a system launch and compress for entry into an existing system.

Scope determination per SKU first (the scope guide's register), including the borderline determinations sought from the operator in writing. Registration data assembled in the operator's format - barcode assignments (market-specific where required), material and dimension data, mark artwork for approval. Physical samples to the recognition programme early: machines learn containers from samples, and the queue in a launch year is the system's scarcest resource. Marking approval closed before plates are made. And the registration's maintenance wired into the change system - a container change (weight, dimension, barcode, mark) is a re-registration event, routed like a declaration change under the documentation station's discipline.

Price architecture: the deposit presented separately from the product price (the consumer's and the law's expectation), system fees and handling flows in the margin model, promotional mechanics checked against deposit rules (a promotion may discount the product, never silently the deposit). Till and invoice data: deposit lines configured in ERP and invoicing, B2B deposit settlement agreed with retail customers (who charges whom at each hand, how refunds reconcile), VAT treatment of deposits per the market's tax rules - an item for the finance team's own advice, flagged here because it is forgotten in a remarkable share of launches. Trade communication: retailers receive the container list, the mark specimens and the changeover dates in their planning cycle, not in the launch month.

Stock: pre-system inventory of unmarked containers has a sell-through window defined by the system's transition rules - plan production changeover so the window suffices, with the marking guide's stock logic, and never let a promotion dump unmarked stock past the window into a market where it cannot be sold compliantly. First season: watch the operator's recognition reports for your containers (rejection patterns by SKU), the return data for anomalies (your containers appearing in the wrong geography), customer-service contacts tagged to deposit confusion, and the reconciliation exceptions in the clearing statements. Assign the watch list an owner with a weekly rhythm for the first two quarters; systems settle, and the settling is managed, not awaited.

Every item on this checklist has the same root: the container is a financial instrument's physical form, and the system admits it only when its data, its marks and its physical samples agree. Producers who internalise that identity - registration as issuance, recognition as acceptance testing, marking as the instrument's engraving - stop experiencing the operator's requirements as bureaucracy and start running them as the quality system they are. The scramble this guide exists to prevent is always the same scramble: discovering the instrument's standards after the printing plates are cut.

Assign the entry a named owner with the four workstreams reporting to one plan: regulatory (scope, registration, operator relations), packaging (marking, recognition, change control), commercial (pricing, till, trade terms), and data (reporting, reconciliation). In small producers the owner wears several hats; in large ones the failure mode is four competent teams without a desk where their deadlines meet. The launch checklist's last line is the recurring meeting - monthly until launch, weekly in the first season - because systems of this kind fail at interfaces, and interfaces are what meetings are for.