Operational before decorative
The website and the app should show the actual work: SKUs, cartons, settlement lines, compliance gates, and exception queues.
About MarginLock
MarginLock exists because FBA sellers do not lose margin in one dramatic moment. It leaks through overweight cartons, mixed prep mistakes, settlement lines that never get reconciled, fee changes that go unnoticed, and reimbursement work that only happens when someone has time to chase it.
The product brings those operating details into one workflow: prepare inventory, pack compliant boxes, ship inbound plans, and review what Amazon paid or still owes after the shipment leaves the warehouse.
How we think
Every part of MarginLock is designed around a simple constraint: the team packing boxes and the owner reviewing margin should be looking at the same source of truth.
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.
The website and the app should show the actual work: SKUs, cartons, settlement lines, compliance gates, and exception queues.
A seller should be able to understand the value, try seeded demo data, and decide whether to connect Amazon without a sales call.
Packing and financial reconciliation are not separate stories. MarginLock treats them as two sides of the same FBA operation.
The live demo uses seeded data, so you can inspect the warehouse and margin-protection loop without a credit card.