For bulky, dealer and multi-drop goods

Put freight on the order — for bulky, dealer and multi-drop goods, run orders, warehouse and freight as one.

For brands and distributors moving heavy, bulky or fragile goods — cycles, appliances, cookware, building materials, auto parts, agri-inputs — set freight rules per SKU by weight, volume and fragility, plan multi-drop loads, and dispatch to scheduled appointments, all on the same record as the order.

This is a focused wedge, not a homepage pitch. It’s for the durables, distributor and 3PL crowd — about 1 in 11 of the brands we work with carry a freight leg, and for a handful of bulky-goods players it’s the whole game.

See freight on the order, on your own SKUs For 3PLs and LSPs
A bulky order line with its freight, by weight, volume and fragility, filled in on the same record, dispatched multi-drop to a scheduled appointment A glass order-record panel on a pale-cyan mesh, headed by a de-identified bulky durable line with a green Live pill. Three freight-rule chips sit on the record — by weight, 42 kilograms; by volume; and fragile — and resolve into a surface-freight charge of rupees 1,180. A short hairline ties the freight cell to an order-total tile of rupees 24,360 with a small node, showing they sit on the same record, not a second system. Below, a flow rail runs from goods-received through a multi-drop dispatch of three numbered drop stops to a scheduled appointment window that the load is sequenced to. Figures are a representative example, not a specific customer’s data.

One record — bulky durable line, freight computed on the order:

  • Freight rule by weight (42 kg), volume and fragility — per SKU attribute
  • Surface freight ₹1,180 — computed on the order as placed
  • Multi-drop dispatch — 3 stops, sequenced to a scheduled appointment window

Order total ₹24,360 — order and freight on one record, no second system

Who this is for

If freight is part of your order, this is for you. If it isn’t, start with orders + warehouse.

Most consumer brands don’t need this — their parcels go out on a courier. But if you ship bulky goods, run a dealer network, or move multi-drop loads, freight is woven into the order.

  • Bulky-durables brands

    • national cycle and durables makers — weight-based surface freight, dealer + D2C
    • an auto-accessories brand — freight by weight, volume, fragility per SKU

  • B2B / building-materials marketplaces

    • a building-materials marketplace — bulk freight, appointment-based site delivery
    • a B2B agri-input marketplace — surface freight to remote rural pincodes

  • Distributors moving full vehicle loads

    • a large distributor — multi-drop load plans, fewer trips
    • a distributor running WMS + freight — GRN through to multi-drop dispatch

  • 3PLs / LSPs

    • multi-client freight (see /for-lsp/)
    See the 3PL / LSP page

What it does

Freight on the order, capability by capability

Freight rules per SKU, freight on the same record as the order, multi-drop load planning and appointment-based dispatch — live today, for the goods that need them.

Live · freight rule per SKU attribute

Freight rules per SKU attribute

The use case

A cycle and a small accessory can’t cost the same to ship; freight must be by the SKU’s own weight, volume, fragility, on every order.

What goes wrong today

Keyed by hand or flat — under-recover on heavy SKUs, over-quote on light ones, reconcile manually after.

What we do

Surface-freight rules per SKU attribute, computed on the order as placed.

Two SKUs priced for freight by their own weight, volume and fragility, on the order A glass panel showing two de-identified SKU rows. A heavy SKU, 42 kilograms, tagged by weight, volume and fragile, resolves to a surface-freight charge of rupees 1,180. A light SKU, 0.4 kilograms, tagged by weight, resolves to rupees 40. A note reads: the rule keys off each SKU’s own attributes, computed on the order, not a flat rate. Figures are a representative example, not a specific customer’s data.

Same order, two SKUs, freight by their own attributes:

  • Heavy SKU 42 kg — weight / volume / fragile → ₹1,180
  • Light SKU 0.4 kg — weight → ₹40
Live · freight on the order record

Freight on the same record as the order

The use case

See freight cost against the order, reconcile against the carrier’s bill, no second system.

What goes wrong today

Orders in one tool, freight in another — every dispatch a manual tie-out.

What we do

Orders + warehouse + freight on one record, freight auto-reconciles. At real volume, an ops headcount you don’t have to add.

One record carrying the order, the warehouse step and surface freight, with freight reconciled against the carrier bill A glass order-record panel with three lanes on one record: an order subtotal of rupees 23,180; a goods-received-note warehouse step; and surface freight of rupees 1,180. They resolve into an order total of rupees 24,360 on one record. Below, the surface-freight figure is matched against a carrier bill of the same rupees 1,180, marked reconciled — no second system. Figures are a representative example, not a specific customer’s data.

One record — order, warehouse and freight:

  • Order ₹23,180 + GRN + surface freight ₹1,180
  • Order total ₹24,360 — order and freight on one record

Freight ₹1,180 auto-reconciles against the carrier bill — no second system

Proof Durables and electricals brands — distributor, web and marketplace orders all need freight: OMS, WMS and TMS as a single system.

Live · multi-drop load planning

Multi-drop load planning + delivery sequencing

The use case

One truck, many drops; you want an optimised load plan and sequence to run fewer trips.

What goes wrong today

Whiteboard / spreadsheet planning — under-filled trucks, back-tracking, more trips than the freight needs.

What we do

Optimised load plans and delivery sequences for multi-drop dispatch.

One truck load, packed and sequenced into four drops in one run A load-plan panel. On the left, one run origin shows a truck with a load fill reading nearly full. A rail runs to four numbered drop stops in sequence — drop one, two, three and four — so the truck carries more and runs fewer trips. A note reads: optimised load plan and delivery sequence; fewer trips than ad-hoc planning. The drops are a representative example, not a specific customer’s data.

One run, packed full, sequenced into four drops:

Drop 1 dealer dock → Drop 2 site delivery → Drop 3 dealer dock → Drop 4 distributor — an optimised load plan and delivery sequence, so the truck carries more and runs fewer trips.

Live · appointment-based dispatch

Appointment-based dispatch for scheduled site delivery

The use case

Steel, cement, tiles, bulk goods go to a project site or dealer dock on a scheduled appointment.

What goes wrong today

Dispatch isn’t sequenced to the site window — trucks wait, sites reject, freight wasted.

What we do

Appointment-based dispatch sequenced to the scheduled site/dealer window.

A dispatch sequenced to hit a scheduled site delivery window A site-delivery schedule strip across the day. A dealer dock window is booked from 2 to 4 PM. The dispatch is sequenced so the load arrives inside that window, marked on time. A note reads: dispatch is sequenced to the scheduled site or dealer window, so trucks don’t wait and sites don’t reject. The schedule is a representative example, not a specific customer’s data.

Dealer dock window booked 2–4 PM:

The dispatch is sequenced to arrive inside the booked window and hits it on time — so trucks don’t wait and the site doesn’t reject the load.

The wedge

Why the freight leg never goes dark

The freight leg isn’t tracked in a second system — it’s written to the same order record as everything else, from order-confirm to signed POD.

Order #BD-7742 one record · no gap
Confirmed order-confirm
Picked up truck leg · 42 kg
At the site multi-drop · appointment
Signed POD on the record

Confirmed, picked up, at the site, signed — one record, no second system’s status to reconcile back.

The freight leg, on the stack you already run.

We own the freight integrations — your job is to ship, not maintain a carrier API.

See every integration

Straight answers

The questions a bulky-goods buyer asks first

We already have a TMS / a freight desk.
The cost isn’t the TMS — it’s the seam between it and your orders. Put freight on the order record and that reconciliation disappears. At volume, a standing ops cost you stop paying.
Our ERP (SAP/Oracle) is supposed to handle this.
Most enterprise ERPs run orders and inventory well and the freight leg poorly — which is exactly why a 3PL in our pipeline pays enterprise money and still can’t do freight. Fretron sits on top and runs the freight leg the ERP doesn’t.
Are you really a freight specialist, or a consumer-OMS dabbling?
The opposite. The engine has run freight at scale at some of India’s largest manufacturers and LSPs — that’s the heritage. What’s narrow is the fit: freight-on-the-order is for bulky, dealer and multi-drop goods, not every D2C brand. If that’s you, this is a deep capability, not a bolt-on.

The proof

Proven where freight is the hard part

Rated 4.4 on G2 and 4.8 on Capterra.

National cycle and durables makers move bulky goods across dealers and D2C on weight-based surface freight. Electricals and appliance brands run distributor, web and marketplace orders that all need freight on the same record. Building-materials and agri-input marketplaces and large distributors across our pipeline are moving for the same reason.

The freight engine has run at scale at some of India’s largest manufacturers and LSPs — that’s the heritage. The fit is narrow: bulky, dealer and multi-drop goods. So we don’t hand you a wall of logos — we compute the freight on your own SKUs, live.

See it live

See freight on the order — on your own SKUs.

Bring a few bulky SKUs and a multi-drop lane. We’ll set the freight rules and show freight computed on the order, live.

Book a demo on your data WhatsApp
  • Live in weeks
  • Your data, your call
  • No rip-and-replace

Priced 1:1 to your dispatch volume and freight stack. Founding-partner terms for early players.

Run a 3PL or LSP? See multi-client freight →

Freight computed on the order line An order line for a bulky SKU. The previously-blank freight field fills by weight times distance, on the same record as the order, so the freight cost is on the order the day it ships rather than in a spreadsheet weeks later.
Illustrative — freight is computed on your own rules and lanes in the demo.
Review build