Designed to sit inside a stack, not replace it.

Accounts, contacts and commercial activity flow from Nexus into ATLAS so Customer 360 shows the same relationship history the sales team sees.

• Account — Company, tier, owner and contract SLA hours seed the ATLAS customer record.
• Activity — Calls, QBRs and escalations appear on the customer timeline alongside shipments.
• Service signal — On-time performance and open exceptions are pushed back to the account record.

Storefront orders land in ATLAS for allocation, and fulfilment status flows back so the shopper sees the same tracking the control tower does.

• Order — Checkout orders arrive with items, payment intent and ship-to address.
• Catalogue — Product and variant definitions map onto ATLAS SKUs.
• Fulfilment — Allocation, dispatch, tracking number and delivery confirmation post back.

Payment capture and refund settlement for prepaid and UPI orders, plus COD remittance reconciliation.

• Payment — Capture and settlement events reconcile against the order payment status.
• Refund — Approved refunds are raised against the original payment.

Card payments and refunds for international and enterprise accounts billed outside INR rails.

• Charge — Charge and dispute events update the order payment status.
• Refund — Refunds raised from the returns workflow settle to the original method.

Rate shopping, label generation and scan-level tracking for international express consignments.

• Booking — Shipment manifest and label request at dispatch.
• Tracking scan — Hub scans map onto the ATLAS shipment event timeline.

Express and priority services with pickup scheduling and proof-of-delivery retrieval.

• Pickup — Pickup requests raised against the origin warehouse dock schedule.
• Proof of delivery — Signature and consignee name attach to the ATLAS POD record.

Ground and air services with time-in-transit lookups for lane planning.

• Booking — Consignment booking with service level and declared value.
• Transit estimate — Time-in-transit feeds the promised delivery date on the order.

Domestic express waybill generation and scan-level track & trace across the Indian network.

• Waybill — Waybill generated at dispatch and stored as the shipment tracking number.
• Scan history — Scan events append to the shipment timeline and drive exception detection.

Surface and express network with pincode serviceability and COD remittance files.

• Serviceability — Pincode coverage constrains which carriers are offered at booking.
• COD remittance — Remittance files reconcile against collected COD on delivered stops.

Geocoding, distance matrix and live traffic for route optimisation. ATLAS ships with an offline schematic map instead.

• Address — Ship-to addresses geocoded to coordinates for stop sequencing.
• Distance matrix — Travel times replace the built-in road-distance estimate.

Vector basemaps and the Optimization API as an alternative renderer for the last-mile board.

• Stop set — Daily stops submitted for sequence optimisation.
• Optimised route — Returned sequence replaces the built-in nearest-neighbour plan.

Material master, purchase requisition and goods receipt synchronisation with the procurement module.

• Material master — SKU definitions and costs stay aligned between ERP and ATLAS.
• Goods receipt — Warehouse receiving posts back against the ERP purchase order.

Invoice, credit note and general ledger posting for the finance workspace.

• Invoice — Customer invoices post to the receivables ledger.
• Credit note — Approved refunds raise a matching credit note.

Transactional email for dispatch confirmations, delivery notifications and return labels.

• Notification — Dispatch, out-for-delivery and delivered events trigger templated email.

SMS and WhatsApp delivery windows, OTP capture for proof of delivery and failed-attempt alerts.

• Delivery OTP — One-time code issued to the consignee for POD verification.
• Reply — Consignee replies drive reschedule requests on the stop.