Staged payments: the leverage structure of a China order.

Why deposits exist at all

A factory taking your order commits materials, line time and, for custom work, tooling before seeing full payment. The deposit covers their exposure to you; the balance covers your exposure to them. That symmetry is the whole design principle: at every point in production, each side should stand to lose something by walking away. Terms that break the symmetry (100% upfront in either direction) put one party entirely at the other's mercy, which is why "full payment before production" from an unproven supplier is a red flag with an invoice attached.

The common structure, and what each tranche is for

Most custom orders run as tranches: a deposit that starts production, sometimes a mid-production payment on larger runs, and a balance held until release. The exact split is negotiated per order. What matters more than the percentages is what each payment is conditioned on. The deposit follows the signed specification and golden sample, not the promise of one. The balance follows a passed pre-shipment inspection, not the shipping deadline, not the factory's assurances, and never the pressure of your own launch date. Tooling is best paid as its own line with its own ownership terms.

Spending the leverage deliberately

The balance payment is the only moment where a quality dispute is cheap to resolve: defects found before release get corrective action, because the factory's money is behind yours. The same defects found after payment are a favour request across an ocean. This is why inspection gates and payment gates belong in the same sentence in the purchase order, and why paying the balance early "to be nice" or to chase a deadline is donating the exact leverage the structure exists to give you.

The agent-native lens: money that waits for evidence

When the buyer sends an assistant. Assistants are starting to do more than draft the payment run, and some are being set up to queue payments. That makes the gate literal. Software releases what it's told to, on whatever condition it can see, so write conditions a machine can check: the purchase order names the inspection standard and who inspects, the balance cites a passed report by its reference, and the payee is the entity on the contract. An assistant can then match invoice to order to inspection result, and refuse to queue a balance with no passed report behind it. Brief it to stop at any mismatch in amount, currency, entity or account and hand it to a person unresolved. On the supplier's side, an invoice that quotes the order number and the milestone it bills is easy for a customer's software to match.

When the business runs on agents. The chart above becomes a live record: for each order, money paid against value delivered, with the evidence for every step attached. Agents can keep it current, book the inspection ahead of the balance date, chase a missing report and assemble each payment with its evidence pack. Two separations keep it safe. The agent that prepares a payment never approves it, and the person who approves reads the inspection report, not a summary of it. When terms relax for a proven supplier, that's a recorded decision with a reason and a named approver, not a habit an agent picked up from the last few orders.

Practicalities that keep it clean

Pay the entity named on the contract. A payee that doesn't match the counterparty is a conversation to have before money moves, not after. Forged invoices and payment requests are getting easier to make convincing, so check every one against the contract you signed, never against the paperwork that arrived with it. Keep the terms in the purchase order rather than folklore, in a form the next person, or the next piece of software, can read without asking. And as trust builds over repeat orders, terms can relax by agreement. That's the relationship maturing, and it's worth more than any single negotiation.