From the operations desk
The situation
Sunday was heavy for a desk whose factories and warehouse were closed. Sellers' support assistants posted after-sales batches in one go — replacements, cancellations, line swaps and a refund request. A daily-invoice client had left a Saturday recap of the previous day's orders. Manual link-plus-address orders arrived in chat, a sample chase came in late at night, prospects turned up with six questions at once, and one seller sent a bare question mark. Almost none of it could be solved on the day. All of it could have been answered.
A closed day still owes a next touch
A weekend message does not need a solution. It needs a stated next touch: which part is answered now, which part waits for a supplier, and on which working day that part arrives. The after-sales batch from the small-accessories store sat for about a day while the assistant re-tagged the same tickets, because nobody had said when they would be worked. A cut-off and a reopening time, pinned in the group, would have made the silence predictable instead of worrying.
The split that worked came from a German prospect who arrived on Sunday morning with six questions. Store connection steps are process-only, so they were answered at once; unit price, pictures and transit were named for Monday when factories open. A sample packed after the logistics cut-off got the same treatment — a named next-day update rather than an open question overnight. The bare "?" was answered with "the warehouse reopens Monday", which was correct and one pinned working-hours line too late.
The working rule on what a closed day can and cannot move is set out in Saturday's note on what the weekend can and cannot move. Sunday's addition is that the acknowledgement itself is the deliverable, and it has to carry a day. The process-only answers — how a store connects, what the flow is, what the FAQ already covers — should never wait for a factory.
Establish the shipping model before the number
Several Sunday enquiries carried a target price with no shipping model attached. A lead filed as a dropshipper turned out to buy sportswear for clubs in small runs — a trial run, then batches of low tens to a couple of hundred to one address. The useful first question was whether the target price assumed one unit to each customer or a batch to one door, because the answer changes the quote entirely.
A prospect holding a few dozen units of a multi-part electronics kit wanted a bulk marketplace supplier beaten. Asking how many orders were pending and why switch was the right opener; the missing step was the bill of materials, since a kit with interchangeable parts cannot be priced from a listing title. Another seller sent two listings of the same family "to compare which is cheapest" — the agent quotes against a specification, not against a reseller's page.
Motive and model come first. If the model is in doubt, the comparison of dropship, pre-stock or an overseas warehouse is the conversation to have before any figure is quoted.
Say whose claim a dispatch date is
A supplier's two-day dispatch promise relayed into a quote is the supplier's claim until goods reach the warehouse. A tracking number uploaded on Monday morning to steady a platform is not a Monday scan; the parcel may leave on Tuesday, and the seller should hear that before promising a customer. Labels and movement are different events, and label created is not the same as shipped is the line to repeat.
Name the next touch before the weekend ends
On a closed day, send the named next touch: what is answered now, what waits for the factory, and the working day it arrives. Before any number, establish the shipping model and the motive, and mark every dispatch date with whose claim it is.