Where a shipment goes wrong between packing and the gate
The FG warehouse is the last check before goods leave the factory. What it misses turns up later: at the buyer’s DC, as a deduction against your invoice, or as a damage claim months after sailing.
A carton mix that does not match the pack list
A ratio carton holds the wrong size split, or a navy carton sits in the black stack. In the playbook’s own example, the pack list says 12,000 pieces and the floor counts 11,988: one carton short. Found at loading, it stops the container while the loading supervisor re-tallies. Missed, it reaches the buyer’s DC, and the dispatch in-charge hears of it weeks later as a deduction.
Nearly 7% of POs
Share of one large retailer’s purchase orders with a supplier fulfillment error, meaning a breach of the PO’s terms, in a 2015 study cited in this paper. All suppliers and products, not apparel alone.
Source: Craig, DeHoratius and Klabjan (working paper), Execution Quality and Chargeback Penalties in Retail Supply Chains (opens in a new tab), 2020.
Carton labels printed to an old packing guide
The buyer’s packing guide sets the label layout, the main and side marks, barcode type and position, carton size and weight, and the pack method. A revised guide arrives by email, the label printing section keeps using the old template, and weeks later the buyer’s DC charges it back against your invoice. The playbook adds one rule for the DC’s scanner: a barcode that will not scan is re-printed, never hand-written.
10% of PO cost
What one US apparel retailer’s compliance manual charges when a supplier packs goods in bulk although the PO says pack-by-store. A similar retailer charges a flat $450. An example rule, not how often it is charged.
Source: Craig, DeHoratius and Klabjan (working paper), Execution Quality and Chargeback Penalties in Retail Supply Chains (opens in a new tab), 2020.
A damp or damaged container, loaded anyway
A container arrives with door rust, a pinhole or a wet floor, and the carrier says it is fine. Loaded anyway, the cartons take on damp and the bottom layer crushes at sea. When the factory stuffs the container, the bill of lading is often marked “shipper load, stow and count”, which can give the carrier a defence, and the claim comes back to you. The playbook’s rule: stop, photograph, raise it with the carrier.
25%
Share of wet cargo damage that, by TT Club’s 2020 claims data, came from water getting in through existing container damage that probably should have been found when the container was packed. All cargo types, TT Club’s own claims.
Source: TT Club, TT Talk – Protecting cargo from wet damage (opens in a new tab), 2021.
Packing changes that land on loading day
A quantity or size ratio changes, or the buyer adds a sticker to every carton days before loading. The packing section re-packs late, and the container may load short. For 50 cartons short on ship day, the playbook says: decide partial or hold by the buyer’s routing guide and tell Merchandising and Logistics within an hour. Its rule for a loading delay over two hours: the FG manager and Logistics are told that shift.
Pack list to gate pass: the dispatch agent’s five jobs
Pack lists, loading reports and gate passes are not among the ERP records the agent reads, so it works from your files and sheets and sets them beside the order copy you upload. Every message or ERP note it drafts waits for an admin to approve or decline.
Pack list totals, set beside the order
Answers with sources
Upload the carton-wise packing list as an Excel or CSV file. Ask for the totals you need: cartons for the order, or pieces for each colour and size you name. The agent calculates it from the actual rows, sets it beside the order quantity on the buyer’s PO or order copy you upload, and lists the rows it used. For a gap, the playbook’s advice holds: look for one whole carton before you re-count piece by piece.
Ask“PO 4471: total pieces of navy size M on the packing list, against the order quantity for navy M on the buyer’s PO.”
Your mark spec read against the buyer’s current guide
Reads your documents
Upload the buyer’s packing guide and your label spec or shipping-mark sheet. The agent sets their text side by side: main and side marks, label content, barcode type and position, carton size and weight limits, pack method. It lists the differences it finds and cites both files. It compares what is written; it cannot see a printed label or test a barcode.
Ask“Do the shipping marks and carton label spec for PO 4471 match the buyer’s current packing guide? List the differences.”
A dispatch readiness summary for the order
Creates files
The agent builds the readiness summary as a document from your packing list and staging sheet: cartons packed, staged and loaded, what is short, and which items on the playbook’s pre-loading checklist are not yet marked done in your checklist or staging sheet, such as the pack list signed by Merchandising. Each line cites its record. Add a second container and it edits that part only; every revision is kept.
Ask“Make the dispatch readiness summary for PO 4471 from the packing and staging records: ready, short, and blocking release.”
A damaged container, raised with the carrier
Acts in your tools
If the empty-container check your team recorded shows door rust, a hole or a wet floor, ask for the email to the carrier or forwarder. The agent writes it from that record, to go out through Gmail or Outlook, with the container number and each fault as written. The email waits in Mavick until an admin approves or declines it, and it is sent only if approved.
Ask“Container 2 for PO 4471 failed the empty-container check: wet floor and door rust. Draft the email asking the carrier for a replacement.”
A hold note on the Odoo delivery, after approval
Reads your ERP
The agent reads Odoo stock transfers and their status. For a delivery held at staging, name the transfer and ask for a note with the reason and the cartons affected, such as “held: one carton short, re-pack under way”. A department admin approves or declines it; the note is added only if approved. Nothing else changes. A note or source document on an Odoo transfer is its only ERP write; Dynamics 365 it only reads.
Ask“PO 4471 is held at staging, one carton short, re-pack under way. Put that note on its Odoo delivery transfer, WH/OUT/00412.”
A short carton at the buyer’s DC, a short container and a gate audit
The buyer’s DC reports a short carton
Dispatch in-charge
The merchandiser forwards the buyer’s DC report: PO 4471 arrived one carton short.
Asks
“The buyer says PO 4471 arrived one carton short. What do our packing list, loading tally and container loading report record for it?”
The agent
Reads the packing list, loading tally and container loading report uploaded for the shipment. Totals cartons for the PO from the packing list rows, then from the tally rows, and sets both beside the loading report’s total and the container and seal numbers in your gate-pass sheet. The seal matters: the buyer’s receiving report should show the same seal, intact. Where a record is missing, it says so instead of filling the gap.
Result
The warehouse’s own records for the shipment on one page, each one cited, ready for the reply to the claim.
A container short on ship day
Loading supervisor
The container loads this afternoon, and 50 cartons for the order are still in re-pack.
Asks
“PO 4471 loads today and is 50 cartons short. What does the buyer’s routing guide say on partial shipment? Draft a WhatsApp to our merchandiser and logistics coordinator.”
The agent
Counts the order’s packed, staged and re-pack cartons from the staging sheet you uploaded, one count per status, citing the rows. Quotes the routing guide’s clause on partial and balance shipment, or says the guide does not cover it. Drafts a WhatsApp Business message to the merchandiser and the logistics coordinator with the counts and the clause.
Approval
The message waits as an action. The FG warehouse manager, as department admin, approves or declines it. It is sent only if approved, and the audit trail records who decided.
Result
If approved, the message goes out with the counts and the buyer’s rule, the notice the playbook asks for within the hour. If declined, nothing is sent.
Gate passes before a buyer’s security audit
FG warehouse manager
A buyer’s security auditor visits next week, and the playbook says gate passes are what auditors check first.
Asks
“For PO 4471 and PO 4480, set each gate pass in our gate-pass sheet beside the container and seal numbers on its loading report. List the passes where they differ or a field is blank.”
The agent
Finds the passes for the orders you name in the gate-pass sheet in Google Sheets and opens the loading report uploaded for each. Sets the container and seal numbers from both side by side, with the vehicle and time on the pass, and marks where a number differs or a field is empty. A report it cannot find is listed as missing. For a whole month, go a few orders at a time. Builds the list as a spreadsheet, citing the row and report for each line.
Result
A cited list for the orders you named: the gate passes to correct or explain, for your team to check against the register before the auditor asks.
What a wrong carton or a wet container costs
These are published figures from research on retailers’ chargebacks, a cargo insurer’s damage analysis and a survey of garment factory managers, cited at the source. None is a Mavick result. A pilot measures your own carton-mix, loading-day and claim numbers.
Fewer deductions for how cartons were packed and marked
60%
Share of the dollar value of one large retailer’s chargebacks that were for execution quality, such as wrong packaging, cartons over the weight or size limit, or carton bar codes put on wrongly. From a 2015 study cited in this paper.
How the agent helps
The agent does not pack or print labels. When you ask, it sets your marks and label spec beside the buyer’s current packing guide, and totals the pack list against the order from your rows. It lists the differences it finds, with both sources, so your team sees it while the cartons are still in the warehouse.
Track: Carton-mix accuracy
Source: Craig, DeHoratius and Klabjan (working paper), Execution Quality and Chargeback Penalties in Retail Supply Chains (opens in a new tab), 2020.
Fewer damage claims you cannot answer
Around 65%
Share of cargo damage incidents that TT Club, a transport and logistics insurer, attributes at least in part to how goods are packed inside the container. All cargo types, worldwide.
How the agent helps
The agent does not inspect containers or look at photos. It compares the loading report with the loading plan for cartons, weight and volume, reads the empty-container check your team recorded, and writes the damage note for the claim file from those records, citing each one.
Track: Damage claims per shipment
Source: TT Club, TT Talk – Protecting cargo from wet damage (opens in a new tab), 2021.
Loading days kept when the order changes late
More than 50%
Share of managers in 73 Cambodian garment factories (2015–2018) who, asked in a survey, rated rush orders, uncertain order size and changes in order size a serious or moderate problem. A whole-factory view, not dispatch alone.
How the agent helps
The agent does not plan the load or decide partial shipment. It counts packed, staged and re-pack cartons from your rows, quotes the buyer’s routing guide on partial shipment, and drafts the message to Merchandising and Logistics for an admin to approve or decline.
Track: Loading-day on-time %
Source: Better Work (ILO and IFC), Sourcing Practices in the Garment Industry: The Root Cause for Poor Working Conditions (Discussion Paper 45) (opens in a new tab), 2022.
What to baseline before a pilot
Measure each one before the pilot starts, then again at its end.
| KPI to baseline | Why it matters |
|---|---|
| Carton-mix accuracy | The playbook targets 100%. One wrong carton means re-packing the source and re-tallying the container, or a deduction at the buyer’s DC. |
| Pack list against physical count | The playbook’s rule: a mismatch above 0.1% of quantity goes to the FG manager, QA and Merchandising within four hours. It is usually one whole carton. |
| First-pass scan rate | The playbook targets 100%: every barcode scans. Mavick does not connect to scanners. It counts from an exported scan log you upload, if the log records failed reads as well as good ones. |
| Loading-day on-time % | The playbook targets 98% or more. A loading delay over two hours goes to the FG manager and Logistics in the same shift, because the carrier charges to reschedule. |
| Damage claims per shipment | The playbook’s target is zero. Each claim goes to Logistics and the Finance insurance desk within 24 hours, and the container photos are what answer it. |
What the agent works from
Records it reads
- Packing list
- Carton label
- Gate pass
- Container loading report
- Loading plan
- Loading tally and staging sheet
- Buyer’s packing and routing guide
- Pre-loading checklist
In your ERP
Reads Odoo stock transfers (status, scheduled date, source document) and Dynamics 365 on-hand inventory by item, site and warehouse. Drafts a note or source document on an Odoo stock transfer; an admin approves or declines it. Pack lists, loading reports, gate passes and the order copy come from your files and sheets. The demo shows what your ERP holds.
One ERP connection serves the whole factory: SAP Business One, SAP S/4HANA, Odoo, Oracle NetSuite, Microsoft Dynamics 365, WFX Cloud ERP or Datatex NOW. This agent reads only the records named above; we check yours on the call.
In your tools
Reads the gate-pass and staging sheets you keep in Google Sheets when you ask. Writes the email to a carrier for Gmail or Outlook, a WhatsApp Business message to the packing supervisor, or a row for your short-shipment register in Google Sheets. Each waits for an admin to approve or decline it, and none is sent or added unless approved.
Tools named today: Gmail, Outlook, Google Sheets, Slack and WhatsApp Business.
Never made up
- Carton counts, quantities, weights or dimensions
- Carton marks, labels or barcode references
- Container numbers, seal numbers or loading dates
- Gate-pass numbers or release approvals
If it is not in your connected data, the agent says so.
Belongs to another department
- Shipping bookings and export documentsLogistics & Shipping
- Negotiating the buyer’s packing guideMerchandising
- Final random inspection (FRI) sign-offQuality Assurance & QC
- Raw-material stores and issue to the floorStores & Inventory
What the Warehousing & Dispatch playbook covers
SOP: container loading
Each shipment gets a loading plan: the carton stacking pattern, the master-carton mix and the port. Cartons are tallied during loading and reconciled against the pack list. The container is photographed at four points: door open, partly loaded, fully loaded and sealed.
Decision rule: a carton-mix mismatch found during loading
Stop loading. Re-tally against the master pack list, re-pack the carton the mismatch came from, and restart only on a clean tally. When the floor counts one carton fewer than the pack list, the playbook says to trace it to packing and, if the carton can be recovered, tell Merchandising before the goods ship.
KPI: loading-day on-time % and damage claims
The playbook has the team review loading-day on-time % each week, against a target of 98% or more, beside damage claims per shipment, where the target is zero. Each day the team looks at loading-day status, the scan rate and mismatches. Ask, and the agent counts any of these from the records you upload, where they hold the data.
Edge case: a container over the carrier’s weight limit
When a container is over the carrier’s stated maximum weight, the playbook says to re-plan: split the cartons across containers, or move some boxes to the next shipment. The agent does not plan the stacking or the fill. If your uploaded packing list carries gross weights, it totals them from the rows when asked, so the total can be set beside the carrier’s limit.
Written as general textile practice and reviewed by four independent AI models. Not yet signed off by a human subject-matter expert. Upload your own SOPs and standards, and every answer shows which source it used.
Ten questions it ships with
The template’s starter questions. Your team can edit them, or ask in its own words.
Packing list for a shipment
Show the packing list and carton breakdown for this shipment — cartons, quantities, weights and dimensions.
Carton marks against the packing guide
Do the carton labels and shipping marks for this order match the buyer’s packing guide? Show both and flag any difference.
Cartons packed, staged and loaded
For this order, how many cartons are packed, how many staged, and how many loaded? Show what remains.
Container loading report
What does the container loading report record for this shipment, and was the load plan met?
Gate passes for a dispatch
Which gate passes were issued for this dispatch, when, and against which vehicles?
Dispatch readiness summary
Prepare a dispatch readiness summary for this order from the packing and staging records: what is ready, what is short, and what is blocking release.
Finished goods ageing
Which finished goods have been sitting in the warehouse longest? Show quantity, order, and days held.
Short shipments this month
Which shipments went out short this month, by how much, and what reason was recorded?
Space occupied by order
How much warehouse space is currently occupied, broken down by order, and which orders are due to ship soonest?
Re-packing done on an order
Was any re-packing done on this order, what triggered it, and how many cartons were affected?
Warehousing & Dispatch: questions before a demo
Can it read barcodes or connect to our handheld scanners?
No. Mavick does not connect to scanners, handhelds or label printers, and it does not read barcodes. If your scanner software exports its scan log as a CSV or Excel file, upload it. The agent counts the cartons scanned for an order from the log’s rows and the cartons on the pack list from its own rows, sets the two counts side by side and shows the rows it used. It is two counts, not a carton-by-carton match. Many scan logs record only good reads. If yours also records failed or keyed-in reads, the agent counts those too, which gives the playbook’s first-pass scan rate. If not, it says the rate is not in the data.
Our buyer’s packing guide is in their vendor portal. Can the agent read it there?
No. Mavick does not log in to buyer portals. Download the guide as a PDF with text in it, not a picture of the pages, and upload it to the dispatch department, up to 10 MB per file. When the buyer revises the guide, upload the new one with its revision in the file name. The agent cites the file behind every answer, so your team can see which revision it compared your marks with.
Can it check our container photos for damage?
No. The agent does not look at photographs or judge a container’s condition. It reads what your team wrote down: the empty-container check, the loading report and any photo list it carries. Keep the photos as your evidence, as the playbook says. From the recorded findings, the agent can draft the email to the carrier, which an admin approves or declines; it is sent only if approved.
Does it read packing lists from our ERP?
No. Carton-wise packing lists, loading reports and gate passes are not among the ERP records Mavick reads. Upload them as Excel, CSV or PDF, or connect the Google Sheet you keep them in. In an Excel file, the first sheet is read as a table of up to 5,000 rows, so keep the carton-wise list there; the other sheets are searched as text. Sales orders are outside the warehouse agent’s ERP reach, so upload the order copy or buyer’s PO beside the pack list. From the ERP it reads Odoo stock transfers, with their status and source document, and on-hand inventory in Dynamics 365. The demo shows which of these your ERP holds.
Will it tell our merchandiser when a container is short?
Only when someone asks, and only with approval. Asked about a short container, the agent counts what is packed and staged from your records and drafts the message to the merchandiser and the logistics coordinator by WhatsApp Business or email. An admin approves or declines the message, and it is sent only if approved. It reads the staging sheet only when someone asks, and it cannot read Merchandising’s or Logistics’ own records.
We ship fabric rolls, not garment cartons. Does it still fit?
Yes, with one limit: the playbook is written around garment cartons, so carton mix, master cartons and carton labels are its terms. A roll-wise packing list works the same way. Upload it, and the agent totals rolls, metres and weight for an order or a shade lot from the rows, and sets them beside the order quantity on the order copy you upload. Your own roll and bale rules can go into the agent’s instructions, which your department head edits and publishes.
Bring Warehousing & Dispatch. We’ll build it on the call.
Book a 30-minute demo (opens in a new tab)- support@mavick.si
- Demo calendar
- calendly.com/safock/30min (opens in a new tab)