Logistics Integration Mock

Every row of the three matrices, executable

Each card is one integration point. The payload is pre-filled and valid — edit it or just press Send.

Received quantity is cumulative — Procurement owns that arithmetic, so it moves when a receipt lands.

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

Capacity is consumed by transport requests, which is what makes the second request in a cycle fail for the right reason.

Seeded out of step with logistics on purpose — a reconciliation that always agrees tests nothing.

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

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

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

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

Both directions. Click a row for the request and response.

auto

Time		Matrix row	Method	Path	Status	ms	Note
No calls yet.