ENTERPRISE
When load planning stops being one person with a screen and becomes part of how the company ships, we build that part with you. The order comes from your ERP, WMS or TMS, the load plan goes back into it, and nobody touches a spreadsheet.
Four situations where the plans on our pricing page stop being enough.
SAP, Oracle, Dynamics, or whatever else your orders live in. The order already exists there, and someone re-types it into a load planner by hand. Enterprise connects the two: the order comes from your system, the plan goes back into it.
Long, heavy or fragile goods, with rules nobody ever wrote down: stacking limits by SKU, temperature zones, hazardous goods, customer-specific requirements. We put those rules into the algorithm.
One shipment carries several orders for several receivers, so the loading order decides the unloading order. The warehouse gets the instruction in your own format, not ours.
Mixed and non-standard cargo by road, rail, sea and air, where more than ten people across sites and shifts have to apply the same rules the same way every time.
Load planning API
No more manual data entry. The order data your ERP, WMS or TMS already holds comes across, the plan is calculated against your rules, and the result goes back where your team already works.
Your ERP, TMS or WMS has the order data: dimensions, weights, packaging, destinations and delivery sequence. It sends that across, together with the vehicles available for the shipment.
The algorithm builds the plan against your rules, checks axle loads and weight distribution, respects stacking limits and the unloading order, and produces the 3D layout.
How many vehicles the shipment really needs and what did not fit, fill rate by volume and by weight, axle loads with a pass or fail, the loading documents, and a link to the interactive 3D plan.
Shipment, items, vehicles, constraints
Plan built and checked against your rules
Plan, fill rate, axle check, what did not fit
Loading instruction in your own format
Shipment, items, vehicles, constraints
Plan built and checked against your rules
Plan, fill rate, axle check, what did not fit
Loading instruction in your own format
A JSON API: your system triggers a calculation and reads back the plan, the summary and the documents. The fastest route when your team can open an outbound connection.
Most large landscapes already have one. We sit behind it like any other service, and your rules about what may leave the perimeter stay in force.
When the API is closed to us, we read the export your system already produces and write the plan back the same way. Nothing changes inside your system.
Procurement asks this before the security questionnaire does, so here it is in plain words rather than in an annex.
Your shipments, your item master and every plan calculated from them stay your property. Nothing you send us is shared with anyone else.
Shipments, your vehicle library and the calculation history, exported without asking us for permission.
During the analysis we write down the loading rules your people follow, which in most companies exist only in somebody's head. That document is yours, and it is worth having whatever happens next.
The question mostly answers itself: the data never leaves your infrastructure in the first place, and the instance keeps running whatever happens between us.
Send us a sample export and your integration constraints. Our team will look at your documentation and tell you which of the three routes fits, before anyone signs anything.
Once the connection is in place, nobody on your side goes looking for a planning tool. Each role gets what it needs where it already works.
Opens a shipment that is already filled in from your system, changes what needs changing, and runs the calculation. The plan goes back by itself. No export, no re-typing, no second tool to keep in sync.
Gets the loading instruction in your own format, on paper or on a tablet at the dock, with the sequence step by step. The yard loads to the plan instead of improvising, and the driver signs for a vehicle that is within its limits.
Sees fill rate and the number of vehicles per shipment in the system they already report from. Every calculation stays in the history, so a plan that worked can be found and repeated rather than reinvented.
This is the part a spreadsheet cannot do, and the reason a plan made by hand costs you a vehicle or a fine.
Goods for the last drop go in first. Nobody unloads three pallets to reach the fourth.
Every plan is checked against the axle limits of that exact vehicle, and against the tolerance around the centre of gravity.
What may stand on what, how high, which way up, and which categories must never share a level.
Segregation your compliance team defined once, applied to every plan after that without anyone remembering it.
Goods onto pallets, pallets into the vehicle, in one calculation instead of two separate guesses.
Some companies want their planners to see CargoTetris. Others want nobody to see it at all. Three levels, and you pick how far to go.
Loading instructions, packing lists and reports in your layout, with your logo, in the languages your sites work in. The warehouse never sees a document that looks foreign.
Your colours, your logo and your own domain, so planners work in something that belongs with the rest of your tools instead of a third-party site.
Your customers plan loads without leaving your portal. The calculation runs behind your interface and CargoTetris is never named to them.
Hosted and kept running by us. Nothing to install, nothing for your team to maintain.
A dedicated instance inside your own cloud account, so the data never leaves your tenancy.
Installed inside your own network, behind your firewall, for companies whose data cannot leave it.
Nothing is built before you have the scope, the price and the timeline in writing.
Kickoff, requirements, and the loading rules your people follow today written down for the first time.
What is possible, what is not, what it costs and how long it takes. In writing, before anything is built. If we cannot build it well, we say so here and not three months later.
Algorithm rules, documents, and the connection to your systems, tested on your own historical shipments.
Your planners and warehouse team start working in the system with us, before it goes live.
Switching over, then changes to the system as your processes change.
Hisense processes 50–70 truck and container loads per day. Shipment data from multiple distributors arrived in different formats, while every load plan had to follow compatibility rules for different appliance categories. The differences in source data slowed down transport planning and increased the risk of loading errors.
Implementation: 3 months
CargoTetris was adapted to Hisense's transport planning rules and product compatibility requirements. Shipment data from distributors was converted into a standardized format, and the system was integrated with the company's IT infrastructure. CargoTetris generated load plans according to a single set of rules and transferred the calculation results to connected systems.
Implementation: 3 months
Midea needed to automate vehicle loading for different appliance categories. Each load plan had to comply with compatibility rules between product groups, prevent damaging combinations and take routing requirements into account.
Implementation: 4 months
CargoTetris was configured with custom compatibility and placement algorithms for different appliance categories. During calculation, the system excluded prohibited combinations and selected a suitable position for each item. API integration with ERP and WMS automated the exchange of shipment data and load plans. Routing requirements were included when forming each load.
Implementation: 4 months
Saint-Gobain needed to optimize the loading of different construction materials during order formation. Each load had to maintain balanced weight distribution, comply with axle load limits and use available vehicle capacity.
Implementation: 5 months
CargoTetris was configured with loading algorithms for different material categories and integrated into the company's ordering system. As products were added to an order, the system calculated their placement, weight distribution, axle loads and remaining vehicle capacity. Distributors could see which additional products could be included while maintaining a feasible load plan.
Implementation: 5 months
EGGER needed to synchronize load planning with its weighbridge system. The process had to identify each arriving vehicle, determine its type, dimensions and capacity, assign the correct shipments and apply product-specific loading rules across five plants.
Implementation: 5 months
CargoTetris was connected to the weighbridge infrastructure through integration gateways. License plate recognition identified arriving vehicles and linked them to planned shipments. Custom loading algorithms accounted for cargo type and weight, while routing logic prioritized loading across five production sites.
Implementation: 5 months
ROCKWOOL used product-specific loading rules based on the experience of planners at different facilities. The rules had to account for product orientation, density, compressibility, geometry, stacking restrictions and protection from crushing. Distributors also needed access to the same calculation logic when preparing shipments.
Implementation: 5 months
CargoTetris converted these operational rules into algorithms for each product group. The system calculated lengthwise or crosswise placement, horizontal, on-edge or end positioning, inner diameter, wall thickness and compressibility. Multi-level loading supported pallets placed on pallets and cargo placed above palletized goods. The calculation engine was integrated into the distributor ordering workflow.
Implementation: 5 months
REHAU needed to optimize loads containing different construction materials. Each load plan had to prevent uneven weight distribution and axle overload while using available vehicle capacity.
Implementation: 5 months
CargoTetris was configured with custom loading algorithms for different material categories and integrated into the company's ordering system. As an order was assembled, the system calculated cargo placement, weight distribution, axle loads and remaining vehicle capacity. Additional products could be included while maintaining a feasible load plan.
Implementation: 5 months
A short description of your cargo, your vehicles and the system your orders live in is enough for a first call. If your case is not one we can do well, we will say so on that call.
We've received your request and will get back to you shortly
