Sunday Merchant Calm: Own Fleet & Overflow

September 20, 2026 / iDeliver

Sunday Merchant Calm: Own Fleet First, Overflow Ready for Monday

Monday parcels do not care that you were peaceful on Sunday. The calmest freight move today is staging the board while the shop is still quiet — own riders first, overflow ready, labels honest, vehicles matched.

This Freight post is for shops and merchants who live in Uyo’s real streets, not a slide deck. Different from last Sunday’s “stage and pick vehicle” checklist — today is about the fleet-versus-overflow decision before the spike.

Own fleet first is not pride — it is clarity

If you run merchants on iDeliver’s route layer, your own riders are the default when they are available. They know your packaging. They know your compound. They know your “fragile upright” voice note without a novel in the notes field.

Sunday is when you confirm who is on tomorrow. Who is offline. Who already has a full bag. A short roster check beats a 10am scramble.

Overflow is a tool, not a failure

When the board spikes — market days, promo mornings, weekend leftovers hitting Monday — borrow vetted platform overflow. That is the design: keep your riders primary, tap the network when volume outruns them.

Wallet honesty matters. You see own-fleet cost versus overflow. You top up before dispatch. No mystery fees after the rider is already moving. Calm accounting is part of calm freight.

Stage parcels while the shop is empty

Seal. Label. Separate fragile from bulk. Match size to the vehicle the flow will ask for — motorcycle for light, car when fragile or heavier, van when the bag is serious. Guessing “bike will fine” on a heavy crate is how Mondays get expensive.

Same-city drops and traveler/corridor parcels are different rhythms. Stage corridor bags with clearer handoff notes and OTP/QR expectations. Do not mix “leave with security” and “must open for receiver” in the same vague line.

WooCommerce and channel orders deserve a Sunday glance

If orders land from WooCommerce or other connected channels, skim Sunday night for anything that will explode at open. Bad addresses. Missing phones. COD surprises. Fix pins and notes before riders are live.

Coverage check before you promise a far pin. If the area is not served, tell the customer early — not after a rider has already burned fuel.

Tracking and handoff for the receiver

Customers still need a live map glance and a clean OTP when required. Share tracking when it helps the door opener. Codes stay private until the real handoff — security desk or the person named on the bag.

COD only when the flow supports it and the shop is ready to reconcile. Tips when the hustle earned them.

Do not mix the three driver worlds

Marketplace driver app is for independent partners on the consumer network. Fleet driver APK is for merchant-owned riders on the logistics engine. MDM is for company-owned Android phones only — never pitch it for a personal rider phone.

Sunday ops stay clean when those doors stay labeled.

Inter-city traveler parcels need Sunday honesty

If a bag will ride a corridor or traveler handoff, Sunday is when you write the receiver’s real phone, the meeting landmark, and whether OTP/QR is required. Vague “someone will collect” notes create Monday drama.

Match vehicle to weight and fragility before you promise speed. Motorcycle for light and local. Car when the load is fragile or heavier. Van when the crate is serious. The network is fast; physics is still physics.

Payouts and wallets for the shop side

Vendors settle in their vendor app world. Merchants on the logistics engine watch fleet-versus-overflow spend in the merchant wallet. Keep those ledgers separate in your head. Mixing marketplace tips with merchant overflow fees is how Sunday calm becomes Tuesday confusion.

Portal for merchant dispatch: merchant.ideliver.ng. Docs for deeper API/WooCommerce setup live at docs.ideliver.ng — keep the consumer blog conceptual; send ops teammates to the docs when they need endpoints.