Logistics Software Development: Connect Orders and Exceptions

SECTION 01

Choose the missing layer, not a replacement by default

A warehouse management system owns warehouse tasks. A transport management system may own booking and carrier planning. Your ERP holds commercial orders and invoices. A custom customer portal can read approved information from those systems without becoming a second owner of stock or delivery commitments.

Review the reporting, portal and connector options you already pay for. If configuration provides the required customer permissions and accurate status, use it. Consider a custom web application when several systems must be presented together or your exception process cannot be expressed reliably in the existing tools.

SECTION 02

Separate the customer order from the physical shipment

An order number is not a tracking number. One order may leave in three parcels, while a consolidated shipment may contain items for several orders. Before designing screens, map order lines, packages, carrier references, warehouse locations and the quantities that connect them. Record which system can correct each relationship.

Carrier information also has access conditions. FedEx's tracking documentation describes different tracking references and restrictions on signature proof of delivery. Treat that as a reminder to verify the selected carrier's actual API permissions, not an assumption that every customer may download every delivery document.

SECTION 03

Illustrative example: one missing carton, not a failed order

Imagine a distributor sends an order in three cartons. Two are delivered; the third has no new scan. This example is hypothetical. A useful portal lists each carton and its latest source timestamp. It displays the order as partially delivered and assigns the unresolved carton to the customer-service queue.

The operator sees the warehouse dispatch record and the carrier event together. They can record a follow-up and publish an approved customer message. AI may draft that message from verified facts, but it must not invent a delivery date or decide that a missing scan proves a lost parcel.

If the delayed event arrives later, the task updates without deleting the operator's notes. A repeated event does not send another customer email. If an event arrives out of order, the integration retains its original timestamp and applies agreed status rules instead of blindly replacing the latest state.

SECTION 04

Add mobile capture only when the workflow needs it

A responsive portal may be enough for warehouse supervisors and account managers. A dedicated mobile application becomes more relevant when approved users must capture photos or scans with unreliable connectivity. Define what remains available offline and how a conflicting update is reviewed after the device reconnects.

Keep carrier credentials on the server. Limit users to assigned accounts or facilities, and avoid placing recipient contact details in public tracking links. Your operations lead owns status meanings; your IT owner controls API credentials and retention; a named support owner handles broken connections and replay requests.

GS1 EPCIS provides a standard for exchanging visibility events. Where trading partners support it, discuss whether shared identifiers and event structures reduce mapping work. A small portal need not implement the whole standard simply because it tracks deliveries.

SECTION 05

Launch one account, one warehouse and one carrier first

For a first release, select one customer account and one supported carrier connection. Include an order search, shipment breakdown, last-update time, exception queue and staff-approved messaging. Defer fleet optimization and a multi-carrier booking engine unless they are the actual reason for the project.

SECTION 06

Ask the agency to demonstrate an exception

Give shortlisted agencies a redacted split-shipment example and ask how their design represents it. Request an integration inventory, supported API assumptions, failure alerts and a cutover plan. A polished dashboard is not sufficient evidence that quantities, permissions and delayed events are handled correctly.

Catapult can scope portals, business-system integrations, controlled automation and mobile interfaces around those requirements. For U.S. or international operations, confirm time zones, units, address formats and support overlap in the brief. Contact us for pricing against the agreed systems and release boundary.

SECTION 07

Frequently asked questions