OMS and pick-pack-ship case study

Order to door, built for drop-day volume.

A single operations backbone for Levents, connecting every marketplace order to a warehouse floor that can pick, pack, QC and hand off to courier without slowing down when volume spikes.

Streetwear retailShopee · TikTok Shop · AmazonOdoo BarcodeCOD reconciliation
12,000

orders in a 3-hour window

25,000

order lines in the same window

3

marketplaces, one queue

The brand

Demand that arrives in bursts.

Levents® is a streetwear label built around fast, high-volume drops. Since launching in 2020 it has grown into one of the most followed local fashion brands in its space, with a Gen Z audience in the hundreds of thousands online and a physical retail footprint to match.

Product moves quickly and in bursts: a single promotion day can outsell a normal week. That is the design constraint for this build. Order intake, picking and courier handoff all have to hold their accuracy at 10x normal load, not just at steady state.

Peak order manifest

ShopeeTikTok ShopAmazon→Odoo OMS→Pick / Pack / QC→Motorbike carrier
12000 ORD // 25000 LN // 03:00 HR
Queue model
Amazon SQS pattern
Pick strategy
Cluster / Odoo Barcode
Settlement
COD day-end match
What we're building

Four systems, one pipeline.

Sequenced the way stock actually moves through the warehouse.

  1. 01
    SourceMarketplaces
  2. 02
    AbsorbOrder queue
  3. 03
    CoreOdoo OMS
  4. 04
    FulfillCluster pick
  5. 05
    DeliverCarrier + COD
01

Nothing goes on the floor unchecked

ReceivingInbound QC

A full quality-control workflow for every inbound shipment: quantity, condition and SKU accuracy verified before stock is released as sellable. It is the checkpoint the rest of the pipeline has to be able to trust.

CatchesMiscounts, damage, mislabeled cartons
OutputClean, trusted on-hand inventory
02

Shopee, TikTok Shop and Amazon in one queue

IntakeMultichannel

Full order detail, including per-channel financial data, pulled from all three marketplaces into Odoo. Built on an Amazon-queue architecture engineered for double-day load: 12,000 orders and 25,000 lines inside 3 hours, without dropped or duplicated lines.

Peak load12,000 orders / 25,000 lines / 3 hrs
PatternAmazon SQS-style queue, built for burst
03

Enhanced Odoo Barcode for speed and accuracy

WarehouseCluster pick

A cluster-pick strategy in Odoo's barcode app fills several orders in one warehouse pass, with each platform's native shipping label printed at the pack bench, cutting travel time and pick errors together.

StrategyCluster picking, multi-order passes
PrintsPlatform-native shipping labels at pack
04

A clean handover, closed out the same day

Last mileCOD

Direct integration with the local motorbike carrier network for parcel handover, plus an accurate day-end consolidation for cash-on-delivery orders, matching what shipped against what was collected before the books close.

HandoffLocal motorbike carrier integration
ClosesDaily COD reconciliation
What changes, in numbers

Projected impact at peak.

Projected, based on cluster-pick and automated-queue benchmarks from comparable Odoo fulfillment builds.

Pick-to-pack time, per order

4.52.7 min

Cluster picking fills several orders per pass instead of one order per walk: roughly a 40% cut from pick release to pack bench.

Pick and ship accuracy

96%99.6%

Barcode verification at every pick, backed by inbound QC that keeps bad stock off the floor.

Order-to-queue time

120 min<5 min

Manual per-channel export during a promotion could run two hours behind. The queue pulls orders in near real time.

Sustained intake at peak

67/min

The target: 12,000 orders and 25,000 lines absorbed in 3 hours without falling behind or dropping a line.

COD day-end reconciliation

3.5 hr25 min

Automated matching of cash collected against parcels shipped replaces a manual tally, with mismatches flagged the same day.

COD mismatch rate, post-close

<0.5%

What is left after automated matching is a short, specific exception list, not a spreadsheet project.

Built for the long run

Not a one-time install.

A system NGYN stays inside of, tuning it against real order data every quarter.

Phase 1 · Months 1 to 2

Foundation

Core Odoo OMS live, all three marketplaces connected, inbound QC and cluster-pick barcode flows running on the floor. Baseline accuracy and timing captured against real volume.

Phase 2 · Month 3

Peak hardening

Queue and pick flow load-tested and tuned against a live double-day promotion. The 12,000 order / 25,000 line benchmark validated under real traffic, not a simulation.

Phase 3 · Ongoing

Continuous optimization

Quarterly reviews of pick paths, queue throughput and COD mismatch trends, adjusting cluster-pick logic and carrier rules as SKU mix, store count and volume grow.

Monitoring

Queue depth, pick accuracy and COD match rate tracked as standing metrics, not just checked after something breaks.

Capacity planning

Before each major promotion, queue and warehouse throughput are checked against the expected order volume.

Embedded support

NGYN works as an extension of the Levents ops team, reachable like an in-house engineer, not a vendor on a ticket queue.

Selling on several marketplaces?

Hold accuracy at peak volume.

If promotion days break your order intake or warehouse flow, the queue, pick strategy and reconciliation can be designed for the burst.

Talk to an Odoo implementation specialist Figures in "What changes, in numbers" are projections based on comparable Odoo fulfillment builds.