overweight warning threshold
Cartons approaching Amazon penalty territory are flagged before a label is generated.
Customer outcomes
Public customer stories will only be published with permission. Until then, this page documents representative workflows that MarginLock is designed to support.
MarginLock
Inbound plan ML-2048
Packing queue
Box 06: 49.8 lb
Attention
Mixed prep blocked
The exception is attached to the shipment record so the operator can resolve it before the workflow moves forward.
Cartons approaching Amazon penalty territory are flagged before a label is generated.
Warehouse actions and post-shipment reconciliation share the same shipment record.
Evaluate the operating flow with seeded FBA data before connecting Amazon.
Representative seller workflow
These are product workflows, not customer claims: they show the operational jobs MarginLock helps sellers complete when FBA shipments and settlement data start to sprawl.
Inventory, reserved units, prep requirements, and inbound-plan status stay in one workspace before a carton is opened.
Weight, size tier, prep category, hazmat, and mixed-box rules are checked before labels print.
Amazon inbound milestones, placement decisions, labels, and shipment status are tracked as one operating loop.
Settlements, fee drift, reimbursement candidates, and per-SKU contribution margin are reviewed from the same source of truth.
Teams sending repeated inbound plans need box-content accuracy, carton weight visibility, and label readiness without rebuilding spreadsheet templates.
Sellers with tight contribution margin need fee drift, settlement variance, returns, and reimbursement candidates visible before month-end review.
Operators can pack and ship from a clear workbench while owners still see the financial exception queue tied to the same shipment history.
The sandbox demo lets sellers review packing, compliance, and margin-protection workflows before connecting Amazon.