TallyPrime and FedEx integration

What moves between them

Shipment records flow from TallyPrime into FedEx. When a purchase order or sales dispatch voucher is created in TallyPrime, ml-connector reads it on each poll cycle, creates a corresponding FedEx shipment, and captures the FedEx shipment ID. Tracking events are then polled from FedEx and written back into TallyPrime as payment or receipt vouchers linked to the original PO, capturing status, carrier name, and current location. The main cadence is tied to your business processes: PO creation in TallyPrime triggers shipment creation in FedEx within the next polling window (5-15 minutes), and tracking updates flow back at the same interval. Reference data such as customer addresses and FedEx account number are stored encrypted and validated on each call.

How ml-connector handles it

ml-connector stores TallyPrime company name, username, and password encrypted, and uses a local agent to reach TallyPrime's port 9000 on the LAN. It polls TallyPrime's Day Book and stock item exports on a 5-15 minute schedule, filters for new shipment vouchers by date range (SVFROMDATE, SVTODATE), and batches them for FedEx. On the FedEx side it exchanges OAuth2 credentials for a bearer token (cached with 1-hour TTL to respect rate limits), creates shipments via the Ship API, and stores the shipment ID in TallyPrime as a reference field. Tracking is polled from the Track API with the stored shipment IDs, and events are written back into TallyPrime via Alter (update) or Import (create) depending on whether the tracking record exists. FedEx rate limits are managed with exponential backoff and a 10-minute cooldown on 429 responses. Because TallyPrime is single-user and has no native idempotency, ml-connector deduplicates by checking for existing shipment references before importing duplicates. Every record carries a timestamp and audit trail for replay if a downstream call fails.

A real-world example

A mid-sized distributor in India runs TallyPrime for accounting and inventory, and ships via FedEx across the region. Before the integration, the warehouse team created shipments in FedEx manually after printing dispatch slips from TallyPrime, then forwarded tracking numbers back to accounting for manual entry into payment receipts. Reconciling AP with actual shipment status took hours each week. With TallyPrime and FedEx connected, dispatch vouchers in TallyPrime automatically trigger FedEx shipments with the correct account number and customer address. Tracking updates populate payment vouchers automatically, so the finance team can see which shipments have been delivered and reconcile invoices without re-keying, saving 4-5 hours per week during month-end close.

What you can do

• •Create FedEx shipments automatically when purchase orders and sales dispatches are recorded in TallyPrime.
• •Sync FedEx tracking events back into TallyPrime as payment and receipt vouchers, matched to the original PO.
• •Store FedEx OAuth2 credentials and account numbers encrypted, refreshing tokens on each API call within rate limits.
• •Poll TallyPrime on a 5-15 minute schedule via local agent, with exponential backoff on FedEx rate limit responses.
• •Maintain a full audit trail of every shipment and tracking record, with replay capability if a downstream write fails.

Questions

Does ml-connector require a local agent to reach TallyPrime?

Yes. TallyPrime runs on a local Windows machine and exposes port 9000 only to the LAN. ml-connector requires a local agent running on the same network or machine to bridge the cloud connector to TallyPrime's HTTP server. Port 9000 must be manually enabled in TallyPrime Settings in the Advanced Configuration menu.

Can ml-connector create FedEx shipments without manually entering account numbers and customer addresses?

Yes. ml-connector stores your FedEx account number and decrypts it on each request. Customer shipping addresses are read from the TallyPrime voucher (via the Group and Ledger entities) and validated against FedEx address data. If an address fails validation, ml-connector logs the error and does not create the shipment, allowing you to correct the address in TallyPrime and retry.

How are FedEx tracking events matched back to TallyPrime purchase orders?

ml-connector stores the FedEx shipment ID in TallyPrime as a reference field on the dispatch voucher. When tracking events are polled from FedEx, the shipment ID is used to look up the corresponding TallyPrime voucher. Tracking status is written back as a new payment or receipt voucher linked to the original PO, creating an audit trail in TallyPrime's ledger.