AxisIQ for logistics and warehousing companies

AxisIQ runs a 3PL's work in one workspace: ASNs and GRNs, stock by client SKU and bin, dispatches, trips, PODs, fleet documents and rate-card billing.

AxisIQ is the operating system a third-party logistics company runs on: one live workspace where client contracts and rate cards, inbound ASNs and GRNs, stock by client SKU and bin, outbound orders and dispatches, trucks, drivers, trips, PODs and client billing all sit in the same database and point at each other. The Logistics & Warehousing template sets that up at signup — seven apps, seventeen record types, five roles, five automation flows, a scan-ready dispatch queue, a pickup booking form, printable challan and lorry receipt layouts, and an operations control tower dashboard — and Ask Axis, the built-in assistant, then adapts it to how your warehouses and fleet actually run.

The work this replaces

Clients send ASNs and orders on email or WhatsApp, each in their own Excel format. Stock is a sheet per client; the bin a pallet went into lives in the supervisor's head. Trips are planned on a WhatsApp group, LR copies and diesel slips pile up in a drawer, and fitness and permit expiry dates sit in a sheet someone checks after a challan. At month end, billing rebuilds storage days, handling units and freight trips from all of it, raises invoices in Tally, and spends a week on the client who disputes them.

The money leaks in the gaps: a GRN never billed, a delivered trip with no POD, a truck booked twice.

What the Logistics & Warehousing template sets up

Seven apps and seventeen record types, linked the way a 3PL's work is linked:

Built-in invoices gain two fields — Contract and Billing period — so every client invoice says which agreement and which month it bills. Trips (TRP-…), dispatch challans (DC-…), pickup requests (PRQ-…) and maintenance jobs (JOB-…) are numbered automatically.

A Client SKU belongs to a client, and Stock counts it per bin and batch, so one warehouse can hold forty brands without their goods blurring. A Dispatch points at its outbound order and, when your own truck carries it, at the Trip. A Proof of delivery points at the trip or the dispatch it closes. A Billable charge carries the same charge types as the Rate card line (storage, handling, pick-pack, freight, COD), so pricing an activity is a lookup against the contract, not a hunt through a PDF.

How a week runs in it

Goods arrive. A client's ASN becomes an Inbound ASN with its ASN lines. When the truck reaches the dock, the receiving team moves it to arrived and unloading, counts each SKU against expected, and records damage. Short units compute themselves. When the GRN is done, a flow raises the inbound handling charge for the received units. Putaway bins are recorded on each line, and Stock shows the result per bin and batch.

Orders go out. Client orders land as Outbound orders with their lines, by CSV import or by hand. Once allocated, an order drops into the Outbound dock queue in Work Queues — To pick → Picked → Packed & labelled → Staged at dock → Loaded & dispatched — and stations scan it forward. At the dock a Dispatch records the challan, carrier, LR or AWB and e-way bill number, and the Delivery challan layout prints the copy that travels with the goods. When the dispatch is marked delivered, the outbound order closes itself.

Trucks run. A load often starts as a Pickup request, booked by a client on the Book a pickup form or by the desk, then quoted and confirmed. The desk plans a Trip with vehicle, driver, LR and e-way bill number, and prints the Lorry receipt & POD layout, which carries a block for the consignee to sign. When it goes in transit, the vehicle is marked on trip so nobody books it twice. Diesel, tolls and driver bhatta are logged as Trip expenses against it. When the trip is delivered, a Proof of delivery record opens, waiting for the signed copy.

PODs come back. The signed POD is checked and marked verified, or disputed with remarks and short units. A verified POD moves its trip to pod_received — the list billing works from.

Month end, billing. Billable charges for the period are pulled onto each client's invoice with its billing period, payments come in by bank transfer or payment link, and the accounting ledger stays balanced for your CA.

Automations included

Five flows ship switched on:

• GRN raises the inbound handling charge — when an ASN's GRN is done, a billable inbound-handling charge is created for the received units.
• Delivered dispatch closes the order — a dispatch marked delivered moves its outbound order to delivered.
• Trip on the road marks the vehicle — a trip going in transit marks its vehicle as on trip.
• Delivered trip opens a POD to collect — every delivered trip gets a POD record waiting for the signed copy.
• Verified POD moves the trip to billing — a verified POD moves its trip to POD received, ready to bill.

Each is an ordinary flow you can edit or switch off in Automation. Storage, pick-pack and freight charges are not raised automatically; enter or import them, or add flows.

Roles

• Warehouse manager — receiving, storage, pick-pack and dispatch for every client.
• Warehouse associate — the dock and the floor: scans ASNs in, picks, packs, hands over dispatches.
• Transport manager — plans trips, keeps vehicles and drivers compliant, chases PODs.
• Billing & accounts — prices activity on rate cards, invoices, collects, keeps the books.
• Client servicing — onboarding, contracts, rate cards, and client questions on stock, orders and PODs.

Each role is editable app by app (permissions).

Your home dashboard

The Operations control tower opens with four numbers: Billable this month, Inbound pending GRN, Orders pending dispatch and Trips on the road. Below them: Billable activity by day, Billing by service over 90 days, On-time delivery over 30 days, Units shipped this month, Vehicles with documents due in the next 30 days, Throughput by client (units shipped, 30 days), and two working tables — Orders waiting to dispatch and Vehicle documents due. Every widget is a SQL query you can change in Analytics.

Platform apps that come switched on

• Work Queues — scan stations; ships with the Outbound dock queue, and you can add one for receiving or returns.
• Invoices & Payments — client invoices and hosted payment links through your own Razorpay account (Payments).
• Accounting ledger — double-entry, exact to the paisa.
• Messaging — email, SMS and WhatsApp through your own provider account; WhatsApp messages to clients and consignees use Meta-approved templates.
• Forms — the Book a pickup form is created and published; opening it to the public internet is the owner's choice.
• PDF document templates — Delivery challan and Lorry receipt & POD, generated from the record and saved to Drive.
• Sheets, Knowledge Base (SOPs, client instructions) and Functions.

Switched off: In-Store Checkout, Marketplaces, Content Studio, Web Campaigns and Calendar — a 3PL has no counter, storefront or ad accounts to run from here. Any of them turns on in Settings → Apps.

Make it yours

After signup Ask Axis asks what is different about your operation, and you answer in plain words:

• "Add a cold-chain temperature field to ASN lines and stock."
• "Every night, raise a storage charge per occupied pallet for each warehousing client."
• "Add a widget for POD pending over 7 days, by client."

Ask Axis changes your live workspace under your permissions and asks before anything destructive. Example data — 8 clients, 22 ASNs, 38 trips, 88 billable charges and more — fills the control tower on day one without firing any automation, and Settings → Industry template → Clear example data removes it in one click, leaving your own records alone. See the AI workspace builder.

What AxisIQ doesn't do

• No e-way bill generation, e-invoicing (IRN) or GST return filing. E-way bill and LR numbers are recorded on dispatches and trips; you generate them on the government portal. GSTIN, HSN and a balanced ledger are there for your CA.
• No Tally sync or export, and no payroll — driver salary is a field, not a payroll run.
• No GPS or telematics feed, and no route optimisation. Trip status is updated by people, or by a flow you build against an API you already use.
• No offline mode. Dock and floor screens need a connection.

Sub-verticals

• 3PL contract warehousing — ASN and GRN, bins, client SKUs, pick-pack-dispatch, rate-card billing and scan stations.
• Transport and fleet operators — FTL and PTL trips, LR and e-way bill numbers, vehicle document expiry, drivers, POD, trip expenses and freight billing.

More industries at /industries.

FAQ

Is AxisIQ a warehouse management system for 3PLs in India? Yes, for the records a 3PL runs on: client SKUs, bins, stock by batch, ASNs and GRNs, outbound orders, dispatches and rate-card billing, with the Outbound dock scan queue ready in Work Queues. It does not include slotting or wave-planning optimisation.

Can AxisIQ keep each client's stock separate? Yes. Every client SKU and stock row carries its client, and bins can be dedicated to one, so stock, throughput and billing split by client.

Does AxisIQ generate e-way bills? No. It records the e-way bill number on each dispatch and trip; the bill itself is generated on the government portal.

How does AxisIQ bill clients on a rate card? Each contract has rate card lines by charge type. Billable charges use the same charge types, compute amount from quantity and rate, and are pulled onto an invoice with its contract and billing period.

Can transport operators use it without warehousing? Yes. Fleet & Drivers and Trips & POD stand on their own; ignore the warehouse apps or ask Ask Axis to remove them.

How do I know which trucks have documents expiring? Each vehicle carries fitness, insurance, permit and PUC validity dates, and the dashboard lists vehicles with documents due in the next 30 days.

Start with the Logistics & Warehousing template — or see AxisIQ in action.