Marketplace

Sign in to shop, or to run the fleet if you are an operator.

Sign in

Create a buyer account

The customer type decides which price lists apply, so it belongs to the account rather than to each order.

Marketplace

Loading the catalogue…

Your cart

Nothing added yet.

My orders

No orders yet.

Logistics Integration Mock

Marketplace · Finance · Transport Management · Notification Gateway

What the systems have exchanged

This stands in for the three external systems Logistics and Sales integrate with — Transport Management, Finance and the buyer's marketplace. Everything below is real traffic between the deployed services; nothing here is simulated in the browser.

Most recent exchanges

The same events as Live traffic, in plain words. Open that tab for the exact request and response.

Transport fleet

What Transport Management assigns from when Logistics confirms a dispatch. A vehicle switched off is never assigned: Logistics gets the next one in the zone, or no carrier at all and the shipment waits at Scheduled. Each assignment uses up capacity.
Loading the fleet…
Add a vehicle
A transport request takes the smallest available vehicle in the destination's zone that still fits the load — so a small vehicle added here is the one the next dispatch will use. The zone must match what shipments carry as their destination, e.g. Addis Ababa.

Every integration point, executable

Each card is one integration point, whether they call us or we call them. The payload is pre-filled and valid — edit it or just press Send.

Financial periods

Click a period to open or close it. A closed period should block a GRN submission unless the user holds Finance Override.

What each counterparty was handed

The tables a test asserts against. Nothing here was delivered to a person or a ledger.

Push into Logistics and Sales

The mock acts as the external system. Orders go to Sales at — the marketplace reaches Logistics only through Sales. Transport Management reports dispatch status straight to .

Per-system behaviour

The matrices mark almost every row "retry required". None of that is testable against a mock that always answers 200.

Scenarios

Each one is a BRD requirement you can put under test in a click.

Queued callbacks

TM assignment, settlement confirmation and refund settlement answer late. Fire one by hand if the mock cannot reach your machine.

Live traffic

Every call in and out of this mock, newest first. Click any row for the exact request and response that crossed the wire.
TimeWhat happenedRequestStatusmsNote
No calls yet.