Published by XiPlush. “We need the plush by the launch” is a useful starting point, but it leaves several dates unresolved. A supplier may be discussing factory dispatch while the buyer is planning the day cartons must reach an event team. Keep those milestones separate before comparing schedules. This guide describes a planning conversation, not a promised production or transit time.
Write the destination and the required arrival first
State where the finished order must be received, who will accept it, and the latest useful receiving date. The public event date may be later than the date your team needs for checking, sorting and distribution. If the venue accepts deliveries only during a particular window, include that constraint. Use an unambiguous date format and specify the local time zone when a receiving cutoff matters. Do not treat “Friday” or “before the show” as a complete instruction.
Ask what the dispatch estimate actually means
Request the proposed dispatch milestone separately. Does it mean production is expected to finish, goods are ready for collection, or the shipment is expected to leave a particular point? These events may require different arrangements. Identify who is arranging transport and what information the freight estimate uses. Ask whether transit, customs procedures and final delivery are included in the discussed scope; do not infer them from a factory production estimate.
Put sample approval on the same plan
Ask the maker which decisions must be confirmed before the production schedule can be agreed. These can include the design reference, sample review, quantities, labels and packing scope. Mark the sample-approval date as a planning dependency rather than an unrelated task. If a sample needs revision, ask for an updated assessment of the remaining milestones. An earlier quotation or tentative slot should not silently become a guarantee after the project details change.
Record who owns each open dependency
A compact plan can have five columns: milestone, meaning, responsible party, current status and next confirmation. For example, “sample approval” needs a clear reference to what is being approved; “dispatch” needs a defined handover point. Leave dates blank until the relevant party confirms them. Add the artwork and quotation versions so that a schedule cannot accidentally refer to an older design. Confirm whether changes to quantities or presentation affect the proposal.
Agree how schedule changes will be reported
Ask who should be contacted when an approval or delivery assumption changes. State the consequence that matters to the project: for instance, items arriving after the receiving window would miss the intended distribution. Discuss possible responses with the supplier rather than inventing a universal buffer or assuming faster freight will solve every delay. A split shipment or a changed method needs its own feasibility and cost confirmation.
Send a brief the supplier can assess
A useful first message is: “Our team needs the order received at [destination] by [date] for [use]. Please assess feasibility for this design and quantity, identify the proposed sample-approval and dispatch milestones, and separate production assumptions from transport assumptions.” Add the actual reference and open questions. XiPlush provides custom plush and OEM/ODM project discussions; sample requirements, charges and schedules are confirmed for the specific design and destination.