How Durian Retailers in Singapore Scale Online Orders

Step 1: Move Pre-Orders Off WhatsApp Chat

A one-person durian operation can run a season on WhatsApp and Google Sheets. The system breaks when a 9pm stock update triggers 300 inbound messages. Customers type “1 box”, “still have?”, “can deliver today?”, and the seller cannot tell which ones paid. The fix is not a website landing page; it is a checkout with exact SKUs and payment confirmation.

Put your order form on Shopify Basic, WooCommerce, or the same storefront you use for Instagram and Telegram. Use the Shopify Buy Button or a Telegram-linked cart so the customer picks a delivery date before paying. Enable Shop Pay, Apple Pay, and PayNow UEN to collect funds without manual reconciliation. If you still accept manual bank transfers, you create a second queue that will jam during peak weekends.

A useful rule: if an order cannot be traced back to a payment timestamp, it is not an online order. It is a chat escalation.

Step 2: Allocate Stock by Harvest Batch

Durian is not a stable SKU. A “Mao Shan Wang 1kg” varies by orchard, harvest date, and weight bracket. If you sell against an aggregated product name, you will oversell your good batches and be forced to substitute lower-grade fruit. That is where refund fights start.

Treat every incoming lorry load as a batch. Label it with a lot number, for example:

`MSW-PJ-0801-M` = Musang King from Pahang, received 1 Aug, medium bracket (1.0–1.2kg).

Then create a matching SKU in your inventory system. If you process more than 200 orders per week, use Odoo’s Lots feature or Shopify’s inventory with weight brackets. Set the available quantity to the number from the supplier’s packing list, minus an 8–10% allowance for damage, oversize, or unripe fruit in that batch.

For pre-orders, sell against a batch that has not yet crossed the Causeway. State the expected arrival date in the product title. If that batch fails, ask the customer to choose a backup batch before you issue a refund. That avoids losing the sale entirely.

Step 3: Route Last-Mile Through Courier APIs

Manual dispatch planning works until you have 150 orders piling into three delivery windows. Calculating routes in Excel takes hours, and one wrong call means a driver crossing Singapore from Jurong West to Changi with a warm box.

Build dispatch on courier APIs instead. Lalamove’s API supports same-day van booking with multiple stops; Pickupp handles scheduled batching; Ninja Van and GrabExpress fit small pulp boxes. Connect these through EasyParcel or AfterShip to push the tracking number back into the e-commerce order automatically.

Use the API to close delivery windows when a van reaches capacity. For example:

– West route: 35 orders per van, 1pm–4pm slot

– East route: 35 orders per van, 1pm–4pm slot

When the west route hits 35, the checkout should show “west 1–4pm not available” instead of accidentally promising an impossible slot. Keep all orders on prepaid payment only. Cash on delivery creates no-show drivers, theft risk, and slower reconciliation.

Step 4: Build Two-Tier Cold Chain for Peak Days

Once checkout and routing are stable, the next failure point is temperature control. A single walk-in chiller filled with cardboard boxes is not enough if the delivery rider opens the door every five minutes.

Use two tiers:

– Tier 1 is the packing room or chest chiller at your operation site. Keep fresh whole fruit at 4–8°C. Frozen pulp must stay at -18°C.

– Tier 2 is the rider’s insulated bag or thermal tote. Use gel packs for fresh fruit. Do not use dry ice on whole fresh durian; it freezes the husk and creates condensation inside the box.

For whole fruit, do not vacuum-seal it. Durian still respires after harvest, and a sealed pack turns humidity into mould. Use perforated corrugated boxes with an internal slip sheet for absorbency. If you process frozen pulp, use double-wall foam boxes and add a temperature logger such as Testo or Elpro to at least one box per dispatch route.

If your capacity cannot hold a batch, close the checkout slot. Better to lose a sale than to deliver a 3kg fruit with a melted pulp core.

Step 5: Track Delivery-Time Refund Rates

Scaling is not about adding more riders. It is about using delivery performance data to pick which slots deserve more volume.

Measure refunds by route and delivery window, not by total sales. A $120 whole-fruit refund weighs the same in Shopify as a $18 pulp-box refund, but they are completely different problems. Tag each order by dispatcher route, for example `west-1pm` or `east-4pm`. At the end of the week, calculate:

`refund value per route / total order value per route`

If the 4pm–7pm east route stays above 6% for two consecutive weekends, reduce the route radius or move the cut-off time earlier. Also log issue tags in the refund reason: late arrival, underweight, unripe, or fermentation smell. AfterShip can give you courier proof-of-delivery timestamps to confirm whether the complaint is the rider’s fault or a check-out problem.

Only after refunds are under 3% per slot should you add a new delivery time or open more inventory.