Implementation

Provide representative order and return examples; product variants and units; channel and warehouse account details; scoped test access; current approval policies; price and tax authority rules; return terms; and the team responsible for unresolved work. Credentials belong in the configured secret store, not in order records or this website.

Identify how competing channels reserve the same stock. Without a common reservation authority, the implementation must preserve an unconfirmed availability state and cannot promise exclusive stock. Agree how warehouse cancellation requests are acknowledged and how finance resolves unknown provider refunds.

Use Proto to propose changes to a reviewable branch. A new field alone is not the complete change when it affects approval scope, quantity invariants or a provider contract. Review the canonical specification, permissions, existing records and acceptance cases together. Keep historical order and price snapshots unchanged unless a traceable correction is required.

Keep the first rollout focused enough to reconcile every order, warehouse handoff and payment result. Add channels and locations as the team establishes a repeatable operating rhythm.