What a packing engine changes in your business.
The engine answers one question - which boxes, and what goes where - wherever that question costs money. Find your kind of business below, then follow it to the problems and integrations that apply.
Online stores
Shops and marketplaces that pack and ship their own orders.
- Shipping is quoted before anyone knows the box, so bulky orders lose money on dimensional weight.
- Packers choose boxes by eye, and the same order ships differently on different days.
- An item that fits no box is found at the bench, after the customer has paid.
- Checkout packs the cart into real boxes and prices them the way the carrier bills.
- Every order gets the cheapest box that holds it, the same way every time.
- A cart that cannot ship is refused at checkout with a reason.
Warehouses and 3PLs
Fulfilment centres and logistics providers packing for many clients.
- Box choice, pallet patterns and crate counts depend on who is on shift.
- Stack limits and handling rules are remembered rather than enforced.
- Every client's rules are a separate habit to train.
- Each packing station gets the carton, the loading order and a printable work order.
- Stack limits, orientation and support are enforced while the plan is made.
- A client's rules are part of the request, so every plan follows them.
Freight and delivery fleets
Carriers, distributors and last-mile fleets loading vans, trucks and containers.
- Vans are loaded in arrival order, and drivers dig for each stop's goods.
- Axle loads are guessed, and an overload is found at a roadside check.
- When the dock does not match the plan, the load is rebuilt by hand.
- Loads follow route order, so every stop's goods are by the door.
- Both axles are checked while the load is planned.
- A change on the dock is recorded and the rest is replanned around what is already loaded.
Software teams and vendors
Teams building an ERP, WMS, TMS or e-commerce platform that needs packing inside it.
- A home-grown packer is a volume ratio with rotations bolted on, and nobody trusts its edge cases.
- A hosted packing API adds a per-call bill, a network hop and someone else's outage.
- When it gets an answer wrong, there is no way to show why.
- One open-source library in Python, PHP, Node.js, Rust, Go, Java, .NET or WebAssembly, with no per-call fee.
- The same request gives the same answer on every run, so results can be cached, replayed and tested.
- Every answer is re-checked by an independent validator, and every item left out carries a reason.
Measure before you decide.
- 01
Export a month of past orders with item dimensions and weights, and the boxes or vehicles you used.
- 02
Run each one through pack() - the HTTP service integration is a ready wrapper for a batch job.
- 03
Compare boxes, cost and items left out with what you actually shipped. The difference on your own orders is the number that matters.