Make vehicle use visible
Review load distribution, usable space and unplaced items before dispatch. Compare vehicle and placement alternatives.
Measure: utilisation and vehicle countEvaluate product handling rules, vehicle capacity and delivery sequence together. Share the 3D load plan with your warehouse and send order, vehicle and driver data to your company’s ERP.

Product rules, load distribution and delivery sequence are evaluated together.
3D views, step-by-step playback and separate loading/unloading documents.
Company endpoints, standard JSON and a recorded delivery outcome.
DeerX brings orders, product master data, stacking rules, vehicle options and delivery stops into one workflow. Loading and routing candidates are compared by loaded quantity, vehicle count, distance, time and utilisation.
Dimensions, weight, fragility, support, top-load capacity and orientation declarations guide placement. A registered GLTF/GLB model is shown in 3D; a measured geometric profile is used in shape evaluation when available. Missing master data and unplaced orders are reported with reasons.
Planning, warehouse and dispatch teams work from the same record. Pilot outcomes are evaluated using your orders and operating metrics.
Review load distribution, usable space and unplaced items before dispatch. Compare vehicle and placement alternatives.
Measure: utilisation and vehicle countGive warehouse staff a PDF showing product position and loading sequence. Review the plan in playback before execution.
Measure: preparation and loading timeCheck fragility, crushing, permitted orientation and support. See why a placement is invalid.
Measure: rule violations and reworkExport saved order, vehicle, driver and route data to your ERP using standard JSON. Track the result.
Measure: manual work and transfer errorsSavings and capacity improvements are measured against a baseline in the pilot; no fixed percentage is promised.
After the server creates the plan, the driver page opens its saved vehicle layout and sequence numbers. Play does not calculate another plan; it visualises the saved loading or unloading order in the 3D scene.
Follow chair and ceramic-carton pallets inside a rigid truck body as a forklift approaches, lifts, carries through the rear door onto the warehouse dock and sets each load down. Choose loading or unloading, playback speed and camera angle.
A fixed sample animation built with real product models: 10 pallet units arranged in two columns and five rows. It does not run a planning or stacking algorithm, and its sequence is not a real order plan.
Drag to rotate · Scroll to zoom
The selected vehicle’s server-validated layout, product identities and loading/unloading sequence numbers are used. The browser does not run a second stacking calculation. If a sequence number is missing or duplicated, playback is disabled and the plan needs review.
Select loading or unloading, a vehicle, cm/kg or in/lb units and a playback speed from 0.5× to 4×. Use previous/next, the step slider and return-to-start controls to navigate.
In loading mode, the next product moves from outside the vehicle to its planned position. Completed products remain in the vehicle as the next step appears. Loads requiring support follow the validated placement and sequence relationships.
In unloading mode, the next product leaves the current load while the remaining products stay visible. A registered GLTF/GLB drawing uses the product’s own model; otherwise the defined group shape is shown. If the drawing cannot be accessed, a temporary group shape and warning appear.
Print separate loading and unloading documents for the selected vehicle or all vehicles, then save them as PDFs in the browser. Documents include step ranges, ordered lists and view diagrams; download the product list as CSV as well.
Each completed step shows the resulting vehicle load; the order comes from the saved loading instructions.
Products leave in their saved unloading order; the remaining load stays visible at every step.
Choose one vehicle or the whole fleet; print the ordered documents with sign-off fields and export the product list as CSV.
The interactive sample depicts forklift, pallet and lifting motion as a visual illustration; its sequence is not a real order plan. For an actual operation, verify the forklift dimensions and manoeuvring space, vehicle/floor capacity, load balance, fork-to-pallet fit and securing method separately. The animation does not prove equipment suitability or approve a real loading operation. A time-limited driver link can display a saved plan without an account.
Fragility, declared top-load capacity, stack count and height are evaluated together. Permitted orientations and which products may support other products are checked.
Palletize products and place the resulting load units into vehicles. Contents, identities, pallet tare and total weight are preserved. Column, 90° and alternating-layer patterns are available.
Include fixed obstacles such as wheel arches and refrigeration units. Define a rear, front, left, right or top entry face and its opening dimensions for the plan.
Compare vehicle types and trip prices. Evaluate complete-kit loading with a SKU/quantity recipe or choose from available cartons; review what remains unplaced.
Keep selected placements in their positions and replan the remaining cargo for that vehicle. Manual moves and rotations go through the same placement validation.
Search, filter and sort saved plans. Link a plan to the dispatch calendar; set daily or weekly repeats within a date range and export an ICS file.
Import data through REST APIs, Excel, CSV and JSON. Send saved order, vehicle, driver and route data to the company endpoint using standard JSON.
Review kg CO₂e for each vehicle’s cargo and deliveries. Use regional references, actual consumption or carrier data; obtain road distances automatically when Google Maps is configured.
Stacking is checked again when delivery order changes. Google Maps road data, the selected vehicle profile and local constraints inform evaluation.
The web interface, calculation engine and integration layer have distinct responsibilities. Warehouse documents, the 3D view and ERP export use the same saved plan.
ERP / REST API · Excel · CSV · JSON
Identity, location, subscription and quota
Stacking rules + fleet and route candidates
3D plan · PDF · sharing · ERP
Vite, JavaScript ES modules and Three.js. GLTF/GLB product models, plan review and loading/unloading playback.
Node.js / Express and server workers. Plans are not recalculated in the browser; the server and CLI use the same core rules.
JWT / API keys, role-based access and company/location scope. Plan records, order revisions and usage allowances are checked together.
REST / OpenAPI contracts, Google Maps road data and company-specific ERP endpoints. Export outcomes are recorded.
The current version uses a JSON data store in a single API process. Hosting, capacity and multi-process deployment requirements are assessed as part of the implementation scope.
Define orders, product dimensions, handling declarations, vehicles and delivery locations.
The server evaluates vehicle, load and route candidates and reports missing data and remaining cargo.
Review the 3D plan, play loading and unloading, and share warehouse PDFs.
Save driver and registration details, then send the reviewed JSON to the company endpoint.
Each company administrator configures an endpoint and Bearer token or API key. The master administrator manages separate connections across companies. Users initiate export from a saved plan preview.
A separate endpoint and authentication for each company. Existing secrets are not returned to the interface.
Complete missing driver or registration details and inspect the standard JSON before sending.
Duplicate protection, delivery history and administrator review for uncertain outcomes. No automatic retry.
An HTTP acceptance by the ERP does not confirm creation of an official transport document. The ERP creates that document; field mapping and acceptance are defined during integration.

Use search, filters and sorting in the plan archive to focus on the relevant dispatch.
Enlarge screen
Use palletizing, fleet cost, fixed placements, kit recipes and carton selection to suit the operation.
Enlarge screen
Review the selected vehicle’s load, distance and carbon calculation in the same workspace. The calculation shown uses sample data.
Enlarge screen
Company administrators configure the endpoint and authentication method. This actual application screen uses an isolated test company.
Enlarge screen
Inspect loaded quantities, driver/carrier data and standard JSON. This screen does not represent a production ERP acceptance.
Enlarge screenCompany and location scope is enforced on the server. Central administration manages subscriptions, features, capacity limits, planning allowances and pricing/payment records per company.
Manages company packages, features, periods, user/location limits, planning quotas and pricing/payment records.
Manages company data, ERP settings, users and locations; views subscription and usage.
Works on orders and plans for assigned locations. Creating a plan requires active entitlements.
DeerX produces a 3D load plan from orders to pallets and vehicles. Placement, loading and unloading sequence, a shareable plan and PDF/CSV output for trucks, vans and containers are in the package.
Yes. Usable cargo space, palletised and mixed loads, orders that do not fit a vehicle and warnings sit in dispatch preparation. Palletizing lives on the same plan.
Yes. The driver plan has separate loading and unloading document outputs. Choose Save as PDF in the browser print dialog. Separate CSV outputs are also available.
Yes. Recipients of an expiring link can rotate and zoom the 3D plan and play loading and unloading step by step without creating an account. The animation shows straight entry and exit passages; forklift maneuvers are not simulated.
The master administrator directly sets each company's package, access period and planning allowance. Company administrators can view their subscription and usage; no license file needs to be generated or uploaded. Renewals, suspension and resumption are managed on the same screen. Commercial scope and support are defined in the quotation and customer agreement.
The calculation follows GLEC 3.2 and ISO 14083 transport-accounting principles. It supports regional and international references, documented consumption and carrier data. Missing values are not treated as zero. Results cover the planned transport legs and do not constitute ISO certification or a full supply-chain inventory.
No. It supports defined product groups including furniture, mattresses, ceramics, construction chemicals and building materials. Correct packaging, dimensions, weight, orientation and stacking declarations are required. A product catalogue is not a customer reference or manufacturer endorsement.
Yes. Orders and master data can be imported via REST API. Send to ERP on the Plans page exports a standard JSON transport document to a company endpoint using Bearer/API key authentication. Field mapping and ERP document creation are configured during integration.
The current version uses Google Maps DRIVE data and local road rules. Google data does not verify every height, axle or heavy-vehicle access restriction. This limitation is shown in the plan and access requires operational checks. The bounded candidate search does not guarantee a global optimum.
Sample orders, vehicle internal dimensions and capacity, product dimensions, weights and verified handling and stacking data. The pilot evaluates vehicle use, loading time and how well the plan works on site.
DeerX supports loading decisions. Final dispatch must also account for actual product and packaging data, load-securing requirements and on-site operational checks.
Share your product groups, vehicle types and ERP workflow. We will define the demo and pilot around acceptance criteria, deployment and support requirements.