Get a phone or email on the order before you ship on a balance due

The argument in one line

If money is still owed when the box leaves your hands, you need a way to reach the buyer that does not depend on a single chat app staying friendly. A username is a conversation. A phone or email is how you finish the order.

Why chat handles fail at the wrong moment

Marketplaces, Instagram DMs, WhatsApp, and similar channels are excellent for discovery and negotiation. They are weak as the only identity on a partly paid order. Handles get renamed. Numbers get recycled. Accounts get banned. People hand the thread to a friend. You are left with a packed order, a deposit you cannot easily match, and no reliable path to collect the rest or arrange return.

This is not a lecture against chat commerce. It is a boundary: chat may start the sale; your order record must finish it.

What to require before pack-out

For any order that is not fully paid—or that is cash-on-delivery, deposit-then-balance, or "pay the rider"—make these fields mandatory on the order you own:

• A phone number you have confirmed with a code or a short call/SMS, or
• An email you have confirmed with a link, and
• The channel handle as optional metadata, not as the primary key.

Confirm once at agreement, not at the door. Put the confirmed value on the pick list and packing slip. If your marketplace already collects a verified phone, copy it into your system of record instead of trusting the chat UI forever. Our note on marketplace leakage is about buyers and sellers going around you; this note is about you still being able to reach a buyer who meant to finish the purchase.

How to say it without sounding hostile

Customers accept clear rules when the rule protects the delivery. Try language like: "We ship balance-due orders to a confirmed phone or email so we can reach you if the rider misses you or the balance changes." Offer a one-time code. Do not demand a life story. Do not store extra sensitive data you do not need.

If a buyer refuses any durable contact, you can still sell—fully prepaid, pickup only, or cancel. What you should not do is ship inventory into silence.

How marketplaces can encode the rule

If you run a multi-seller marketplace, do not leave this to seller folklore. Encode it:

• Order states distinguish fully paid, balance due, and cash-on-delivery.
• The pack action checks for a verified phone or email on balance-due and COD orders.
• Sellers see a blocking reason in plain language, not a generic error code.
• Buyers see why you ask: so the rider or courier can finish delivery and payment.
• Trust and safety can audit sellers who repeatedly try to bypass the gate.

For single-shop social sellers, the "system" might be a store order note field plus a packing checklist. The principle is the same: the ship decision reads a durable contact field you own.

Deposits need matching discipline. Record the deposit against the order id, not only as a chat screenshot. When the balance is collected, the same order closes cleanly. Disputes get harder when money and identity live only in a disappearing thread.

International and cross-border chat sales add time zones and substitute freelancers. Durable contact is how a teammate finishes someone else's order on a Saturday without scrolling three apps for a nickname.

When a handle goes dark after deposit, your playbook should say whether you hold the goods, attempt the durable contact, refund under policy, or escalate to platform mediation—and after how many days. Improvisation here burns inventory and goodwill together.

Wire it into the marketplace or store ops

• Block the "mark ready to ship" action when balance due and contact missing.
• Show the gap on the seller's packing screen in plain language.
• For multi-seller marketplaces, make the rule platform-level so honest sellers are not undercut by sellers who skip it.
• Keep the contact with the order for support and disputes; restrict who can export lists.

We design marketplaces and post-transaction flows where the order record outlives the chat thread. If your deposits are piling up against quiet handles, talk to us.

Sellers sometimes fear that asking for a phone will kill the deal. In practice, buyers who intend to pay a balance usually accept a one-time confirmation code when you explain it protects delivery. Buyers who refuse every durable contact after a deposit are telling you something about completion risk. Believe them early, while the goods are still on your shelf.

Write the refusal path into policy: full prepayment, pickup only, or cancel and refund the deposit under published terms. Ambiguity here is how arguments start in public comment threads.

Keep the confirmed contact only as long as you need it for delivery, balance collection, and dispute windows, then apply your normal retention rules. Collecting a phone is not permission to add someone to a marketing list. Separate those purposes explicitly in your copy and your systems so a packing rule does not become an accidental spam problem.

Train packers to glance at the contact field the same way they glance at the address. If the field is empty on a balance-due order, the line stops. Do not rely on a manager memory. A blocked scan or a red banner on the pack screen beats a verbal rule delivered once at morning huddle.

If your marketplace app cannot block pack yet, use a printable pack list that omits balance-due orders missing contact, and reconcile exceptions daily. Temporary paper controls are better than silent ship.

Measure completion: share of balance-due orders that ship with verified contact, and share that stall at the pack gate. Those two numbers tell you whether the rule is real. If packers routinely override, the override needs a reason code and a weekly review—not a silent habit.

Customer messaging should stay short: one reason, one confirmation step, one place the number or email will be used. Long privacy essays at pack time get skipped. Link to the full policy for people who want it, and keep the order flow moving for everyone else.

Related work: Paddle8.