Bottom line up front: ninety percent of mispicks in an OMS don't start with the warehouse picking the wrong item. They start with a note written in the wrong place, for the wrong reader. Order notes must be split into three types — operational notes, customer service notes, and logistics notes — each with a fixed author, a fixed field, and a fixed reader. Miss any one of the three and things go sideways.
How One Casual Remark Kills an Order
March 2024, a 3C electronics seller in Shenzhen doing about 800 orders a day. A customer service rep wrote "throw in two samples" in the order note, meaning free gifts with the shipment. The picker saw an order-level note and read it as "replace the ordered items with two samples." Two freebies went out; the actual product never shipped. The customer escalated, and the reship plus return freight cost over 400 yuan on a single order. I've seen this exact failure three times. All three times, the word "samples" was the culprit.
September 2024, an apparel seller in Hangzhou. The rep noted "customer wants SF Express ground, worried about loss" — and typed it into the picking note field. Picking went fine, but the packing station printed the label as SF Express ground per the note, while the OMS routing rule said default to YTO Express. Label didn't match the system waybill number, and the parcel sat at the sortation hub for two days. One-star review. A logistics instruction landed in an operational note field, reached the wrong reader, and triggered the wrong action.
Same root cause in both cases: notes had no categories. Everyone typed into the same box, and everyone interpreted it their own way. It's a miracle anything shipped correctly at all.
The Method, Step by Step: Standardizing Three Note Types
Step one: separate the three types, print the table, stick it on the wall.
| Note type | Written by | Written in | Read by | Format template |
|---|---|---|---|---|
| Operational | Warehouse supervisor, or ops staff relaying CS input | OMS operational note field, line-level preferred | Pickers, packers, QC | [Pack] two layers of bubble wrap; [Pick] Zone A before Zone B |
| Customer service | CS reps | CRM / after-sales note field — never in OMS flow fields | CS and after-sales staff | Promise plus deadline, e.g. "promised customer reship before May 8" |
| Logistics | CS reps, or auto-populated by OMS rules | OMS logistics field | Label printing, shipment verification | Carrier plus service, e.g. "SF Express ground, insured" |
Step two: whoever writes a note must first answer three questions. Who is it for? At which step will they see it? What action should they take after reading it? If any question has no answer, the note doesn't get written. That's why "ship it today if possible" is garbage — the warehouse has no operation called "if possible." Either it goes through the expedited flow (with a defined SLA and owner) or it doesn't get written.
Step three: freebies, exchanges, over-ships and short-ships all go at line level. Never at order level. The standard format: "[Freebie] SKU-A001 x2, include with order, excluded from fulfill quantity." SKU, quantity, and whether it counts toward fulfillment — all three elements are mandatory. Order-level notes are only for whole-order matters, like "[Whole order] customer requested two parcels."
The Counterintuitive Part: The Best Note Standard Is 80% Zero-Note Orders
A note is a patch. Too many patches means the system has holes. High-frequency notes like "add bubble wrap" or "include samples" should become system fields or packing rules instead: tag the SKU as fragile and the pack station prompts automatically; build freebies into order promotion rules so the OMS adds the gift line on its own. Handwriting it every time means handwriting it wrong eventually — and the cost of one mistake pays for configuring the rule ten times over.
The trade-off sits right here: the freer the notes, the happier CS is and the worse the warehouse suffers. The tighter the standard, the more CS complains during the first two weeks — but three months later, when the mispick rate drops, everyone goes quiet. What I tell clients: CS gets two weeks to vent; from week three, non-compliant notes get bounced back for rewrite. Not a fine — just "write it properly or it doesn't go through."
Go-Live Eve Checklist: Four Things Before You Sleep
- Print one test order with one note of each type. Grab three random warehouse staff and ask: who wrote each note, who is it for, and what do you do after reading it? One wrong answer means the field design or the training isn't ready — go back and fix it.
- Export three months of historical notes. Full-text search for "try to," "ASAP," "please help," "kindly note" — rewrite every one into an executable instruction, and delete what can't be rewritten.
- Lock down field permissions: CS can't write operational notes, the warehouse can't edit logistics notes. Wrong permissions make the standard worthless paper.
- Add a "read the note" action to the SOP for each note type: picking reads operational notes, packing reads operational notes, shipment verification reads logistics notes. A note nobody reads is a note that was never written.
The Hall of Shame: Common Failures
- "Customer said ship half first" at order level → split shipments must be line-level: which lines ship now, when the rest ships.
- After-sales reships sharing the same note box as normal orders → reships need their own document type, with the original order number in the note.
- A phone number in the note asking the warehouse to call the customer → the warehouse has no outbound-call role. That request goes through the CS callback process. Don't make the warehouse do CS's job.
Before your next warehouse go-live, get the three note types' fields, permissions, and SOPs configured first — that alone prevents half of all mispicks. The other half is covered by the checklist above.
By Lin Xiao, WMS Implementation Consultant
