Connect production, receiving and confirmed demand, with a clear decision when deliveries differ from the plan.
What you start with
Follow the operation
Who takes this stepCampaign team
Resolve reward tiers to final product references and validate recipient details. Your campaign tools retain pledge, funding and customer-promise information; fulfilment needs the confirmed physical demand.
Resolve reward variants and missing recipient details before releasing their orders.
Who takes this stepMerchant / supplier coordination
Prepare an inbound plan with product quantities and carton or pallet contents. Review delivery slots, request a booking and submit the plan using its current version.
The submitted plan gives the warehouse an expectation; booking and physical receipt remain operational steps.
Who takes this stepReceiving operator
Receiving establishes what actually arrived. Review the plan status and reconciliation rather than promoting the supplier's declared quantity directly into available stock.
Send the discrepancy to the campaign and supplier teams so they can decide the replenishment and customer response.
Who takes this stepCampaign owner → order integration
The campaign owner selects orders for release against confirmed stock and retains uncovered demand for follow-up. Import the selected batch and resolve rejected rows before relying on its order count.
Your release policy determines the recipients; Ysend gives the warehouse the validated demand you supplied.
Who takes this stepCampaign team, supplier and warehouse
Arrange any missing units and follow their receipt before releasing a subsequent batch. Connect each wave to its shipments so your campaign team can distinguish dispatched rewards from outstanding commitments.
Confirm the new stock position and import results before closing the campaign's fulfilment backlog.
A reward tier resolves to a specific SKU, quantity and validated recipient.
Supplier contents, delivery arrangements and warehouse receiving responsibilities are understood.
Your team can decide who ships first and how remaining commitments are followed.
Through the Ysend API you can announce an incoming delivery, check delivery slots, submit the plan and see any gap found at receiving. Only the latest version of a plan can be submitted, so an outdated copy cannot overwrite it. Confirmed orders are sent only after your decision.
Authorised users follow inbound plans and orders from the merchant workspace. Warehouse teams record physical receipt through supported operational screens.
Applications