Operations · Module
Supply Chain & Logistics
Shipments with the right carrier, valid e-way bills and proof of delivery
Supply Chain & Logistics moves goods out, in and back with carrier selection, the e-way bill lifecycle and live tracking to proof of delivery. A shipping thin core is planned with Inventory in W4; the full module in W5.
What it does
Supply Chain & Logistics is designed to move goods with the right carrier, valid statutory paperwork and live visibility to proof of delivery, at known freight cost. Shipments are created from Inventory dispatches, transfers, returns to vendor and Commerce orders, with packages, weights, dimensions and consignee from the shared party and address.
Carriers and booking
Carriers and transporters are Organization roles with services (surface, express, FTL, PTL) and contracts. Rate cards by zone or lane, weight slabs, COD and fuel surcharges, pincode serviceability and lanes with transit times feed carrier selection rules. Booking through courier and aggregator APIs returns AWB or LR numbers, labels and manifests. Transporter load tenders go to several transporters on the portal or WhatsApp.
E-way bills and tracking
The e-way bill lifecycle (generate Part A and Part B, update vehicle, consolidated e-way bill, extend, cancel, handle rejection) runs through the Tax Engine and GSP. A validity watch compares validity with shipment ETA and tracking, and warns early with an extension proposal ready. Every e-way bill Action needs a human approval. Tracking events from carriers and telematics are normalised, with exceptions for delay, NDR, damage and loss. e-POD is captured by photo, signature, OTP or recipient name.
After delivery
NDR handling offers customers re-attempt or address correction on WhatsApp. Freight accruals are audited against carrier invoices, COD remittance is reconciled with Finance, and a control tower shows all shipments by status and risk.
Availability
A shipping thin core (shipment record, single-connector AWB booking, tracking status and e-POD) is planned with Inventory in W4 so order-to-delivery can close. The full module is planned for W5. All regulatory rules are to be verified.
Features
What Supply Chain & Logistics includes
Shipment thin core (W4)
Shipment record per dispatch or order, single-carrier AWB booking, tracking status and e-POD so order-to-delivery closes in W4.
Shipment creation
From dispatches, transfers, returns to vendor and Commerce orders, with packages, weight, dimensions and consignee.
Carrier master and lanes
Carriers as Organization roles with services and contracts; origin–destination lanes with transit time and cost benchmarks.
Rate cards and serviceability
Rates by zone or lane, weight slabs, COD and fuel surcharges, and pincode serviceability imports.
Carrier selection and booking
Rules by service level, cost, serviceability, COD, weight and performance; API booking with AWB/LR, labels and manifests.
E-way bill lifecycle
Generate, update vehicle, consolidate, extend, cancel and handle rejection through the Tax Engine and GSP (rules to verify).
E-way bill validity watch
Validity compared with ETA and tracking, with early warning and a prepared extension proposal.
Tracking events
Webhook or polled carrier and telematics events normalised to standard statuses and exceptions.
Proof of delivery
e-POD by photo, signature, OTP or recipient name via driver app, carrier API or WhatsApp, attached to shipment and invoice.
Returns and NDR handling
RTO and customer return pickups linked to Inventory; NDR re-attempt or address correction over WhatsApp.
Customer notifications and tracking page
Dispatch, out-for-delivery, delivered and exception messages with a branded tracking page.
Freight audit and COD reconciliation
Expected freight vs carrier bill by rate card and weight with disputes; expected COD vs remittance with Finance.
Load tender and consolidation
FTL/PTL tenders to multiple transporters; shipments combined by lane and vehicle capacity with consolidated e-way bills.
Control tower and carrier scorecard
All shipments by status and risk; on-time pickup and delivery, damage, NDR rate and cost variance per carrier.
Workflow
Carrier selection and exceptions
- 1
A shipment is planned and serviceability is checked by pincode
- 2
Rate cards and carrier scores rank options by cost and ETA
- 3
Within an auto-book policy and budget the shipment is booked; otherwise a coordinator approves an option
- 4
Tracking events are monitored
- 5
Delay risk triggers an alert and e-way bill validity check; NDR triggers WhatsApp options to the customer; damage opens a claim
- 6
Delivery closes with POD
Workflow
E-way bill lifecycle
- 1
The Tax Engine rule says an e-way bill is required
- 2
Part A is prepared from document data
- 3
It is generated with Part B, or Part A only until the vehicle is known
- 4
Vehicle updates keep it active
- 5
If ETA exceeds validity minus a buffer, an extension proposal is raised for human approval
- 6
It completes on delivery, or is cancelled or rejected within the permitted window
AI
AI skills and Digital Employees
Carrier selection proposals
Ranks carriers by serviceability, rates, performance and ETA; books within freight budget once earned.
E-way bill preparation
Prepares proposals from the invoice or challan and vehicle details; generation stays human.
Validity watch
Predicts ETA against validity and proposes extensions or Part B updates with location and reason.
Delay prediction
ETA risk from lane history, carrier performance and tracking gaps.
NDR handling
Messages customers with options, understands replies and instructs the carrier using approved templates.
Freight invoice audit
Line checks against rate cards and weight, with dispute drafts for human approval.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
When is shipping available?
A shipping thin core is planned with Inventory in W4. The full Supply Chain & Logistics module, with rate cards, multi-carrier booking and the full e-way bill lifecycle, is planned for W5.
Can an agent generate or extend an e-way bill?
No. Agents prepare proposals and warn about expiry. Generation, vehicle update, extension and cancellation always need a human approval.
Which carriers will be supported?
Courier and aggregator APIs are planned per connector. Each provider's API terms must be verified before it is listed.
Is this legal advice on e-way bill rules?
No. E-way bill rules are recorded in the Fact Register and must be verified; please confirm with your tax adviser.
See Supply Chain & Logistics in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.