EDR Freight — Priority Flows

Portal Side
Contract Signing · Booking · Payment

A step-by-step walkthrough of the same three flows, driven live as the real customer — every screen, button, and validation message as the account actually saw it.

Driven live against the shared dev environment (edr_dev)
Personas: hager@gmail.com (Hagernesh Tadesse) for contract & booking; nati@gmail.com (NAti Wondish) for payment
Companion document to EDR-Freight-Priority-Flows.pdf (backoffice/staff side)

Contents

  1. 1. Contract creation & signing — Home, Contracts list, the New Contract wizard (Setup → Cargo/Route → Review), the unit-rate quotation approval step, the duplicate-contract validation, and how/where a customer signs once EDR approves.
  2. 2. Booking — the Bookings list and the document-review flow a customer works through on an existing booking.
  3. 3. Payment — the customer's Invoices page, filtering to what's actually payable, the invoice detail screen with its "Pay" action, and the bank-transfer steps behind it.

1 · Contract creation & signing

Portal customer hager@gmail.com, logged into the freight portal (localhost:5273).

1
Sign in
The portal login form. A customer signs in with their email and password — no OTP step for an already-onboarded account (OTP only applies during self-signup).
2
Home
Landing page after login: quick stats and shortcuts into Contracts, Bookings, and Invoices.
3
Contracts list
The customer's contracts: one Active (CTR-2026-00043, Fully Executed) and two In Progress (CTR-2026-00086, CTR-2026-00087 — both Submitted, awaiting EDR review). "New Contract" starts a fresh one.
4
New Contract — Step 1: Setup
Operation Type, Contract Kind (One-Time vs. Framework), New-vs-Renewal, and the Service Type cards — the entry point of the wizard.
5
Step 1 filled — Operation Type + Service
Operation Type set to Import and "Rail Transport with Customs" selected — this reveals the trucking/customs options below (first mile, last mile, and the included customs clearing service).
6
Step 2: Cargo & Route
Cargo scope (containerised, both 20ft/40ft), and the origin/destination yard pair that defines the route.
7
Step 3: Review & Submit
Final review of the assembled contract terms — operation, service, route, cargo scope, and customs handling — before submitting.
8
Approve your quotation
Submitting immediately opens a per-unit rate quotation for the customer to approve — freight rates for 20ft/40ft containers plus the customs clearance service fee per container size. The dialog is explicit that these are per-unit rates, not a total: the payable amount is computed per booking from the quantities actually shipped. Approving submits the contract for EDR staff review.
9
Real validation: duplicate contract blocked
Re-submitting a route/service/cargo-scope combination that already has an active or in-review contract is rejected outright, naming the conflicting contract by number. This is a genuine business rule hit live, not staged.
Once EDR approves the contract, the customer signs it A submitted contract moves through EDR review as: Submitted → Pending Approval → Approved → Approved Pending Signature → Contract Ready. The "View & sign contract" button only appears once the contract reaches Contract Ready — it shows on the Contracts list row and on the contract's own detail page, and opens a dedicated preview-and-sign page (/contracts/:id/view), not a plain button on the detail page.
  1. EDR staff approve the contract and price it.
  2. The customer is notified the moment it's ready to sign — SMS, email, and an in-app notification all fire together (per the customer's description of the real notification flow — not re-verified against the notification-sending code for this document).
  3. The customer opens the notification or the Contracts list, clicks "View & sign contract", scrolls the full contract text, and ticks the consent checkbox.
  4. They draw or reuse a saved signature, upload a company stamp, then verify by OTP (sent to their registered phone/email) to finalize the signature.
  5. Status moves to Signed — Awaiting Staff, then Fully Executed once EDR counter-signs.
CTR-2026-00086 and CTR-2026-00087 above are still at Submitted — EDR hasn't approved them yet, so no sign button is showing for either.
11
Where "View & sign" actually shows (a different customer's contract list)
A second real account (nati@gmail.com, 17 contracts) confirms the button live: its Action column carries "View", "Request shipment", "Book shipment", and "Initiate booking" depending on each row's status — the same column shows "View & sign" the moment a row reaches Contract Ready.
The signable window is real and it closes This account's own CTR-2026-00089 was captured with a live "View & sign" button two days ago (per the customer's own screenshot) — by the time this document was rebuilt, that same contract had already moved to Expired with no button left to click. Contract Ready is a real, time-boxed state, not a permanent one. No currently-open contract exists on either test account at time of writing, so the sign page itself (scroll-to-consent → draw signature → stamp → OTP) could not be re-captured live in this pass; it was documented from the customer's own screenshots and code inspection instead.
10
Fully executed contract — signatures
CTR-2026-00043's detail page: both STAFF and CUSTOMER signatures are complete and the contract is Fully Executed — the end state of the flow described above.

2 · Booking

A portal customer does not have a bare "New booking" button on the Bookings page itself — booking creation is triggered from a signed contract's row, once EDR has cleared it for shipment (contract status Active). What that entry point actually is depends on the contract's state: "Initiate booking" opens a brand-new booking; "Book shipment" / "Book" continues one EDR has already pre-cleared.

1
Initiate booking — confirmation
Clicking "Initiate booking" on an Active contract (CTR-2026-00071) doesn't create the booking immediately — it confirms first: "This creates a new shipment booking under contract CTR-2026-00071. You'll upload the import documents next, and the shipment quantity is drawn down from your contract's reserved capacity." Cancelled here rather than completed, since creating a live booking is a real mutation.
2
Complete Your Booking — cargo details
Following an already-cleared booking's "Book" action (BK-2026-000209, Bulk cargo under CTR-2026-00093) lands on this form: the contract's fixed route, a cargo-details block (Total weight for Bulk cargo — a Container-scoped contract shows an Excel-import table instead), and a Schedule block picking the binding shipment day. The billing currency here is fixed to ETB, paid through the payment gateway. The calendar is real and reactive: it read "Enter your cargo details first — available shipment days depend on the wagons your cargo needs," and no day was actually open on this route at the time of capture (0 available days) — the same live batch-window behaviour documented in Section 1.
3
Bookings list — one contract's view
This account's one existing booking, BK-2026-000068 on CTR-2026-00043 — status "In review," amount still ETB 0.00 because pricing is finalised after document review, not at booking creation. Every row carries a "Review documents" action.
4
Import documents dialog
Clicking "Review documents" opens this in place, no page navigation. All four required import documents — Bill of Lading/Waybill, Packing List, Import declaration, and Ethiopia T1 & Djibouti T1 — show status "Under review," each with View/Download and a "Replace file" drop zone. The banner is explicit: "Only re-upload the documents flagged with a query below — approved documents stay as they are." "Submit documents" stays disabled while nothing is flagged.
5
Bookings list — the fuller picture (nati@gmail.com, 38 bookings)
Across a larger real history the Action column carries every state at once: "Book" (cleared, awaiting cargo details), "View" (nothing to do), "Rebook wagons" (a cancelled reservation), "Pay [amount]" (booked, payment outstanding), "Review documents" / "Documents", and "Track" once a train is assigned. BK-2026-000188 shows "Pay 16,323.25 ETB" while its own Status column reads Cancelled — a live inconsistency (the booking lapsed after its payment window closed, but the stale Pay action hadn't been cleared from the row).

3 · Payment

The customer-facing payment surface is the Invoices page.

1
Invoices — hager@gmail.com (nothing to pay)
Outstanding, Overdue, and Total Invoices all read 0. This lines up with the Booking flow above: BK-2026-000068 is still in document review and hasn't been priced, so nothing has been invoiced to this customer yet. The customer supplied a second real login (nati@gmail.com) to reach the actual payment screen.
2
Invoices — nati@gmail.com, filtered to Due
This account has a long invoice history (35 invoices) and 5 currently Outstanding. The status filter's real options are Due / Overdue / Paid / Draft / Cancelled / Refunded; filtering to "Due" narrows the list to what's actually payable right now, each row with a "Pay" action.
3
Invoice detail — the Pay screen
Opening INV-20260820-00017 (Br 200.00, a port-charges line item off booking BK-2026-000112) shows the full detail a customer sees before paying: billed-to company, source, issue/due dates, the line-item breakdown, a "Download invoice" action, and a "Pay Br 200.00" button sized to the exact amount due.
What "Pay" opens (from the customer's own screenshot) Clicking "Pay" opens a "Complete your payment" dialog: the amount due, a red warning — "Pay only from a bank account registered under your company name — DE BE KE. A payment sent from an account under any other name will not be recognized as paid" — a payment-method picker (the option shown was CBE Bill Payment — "Pay at any CBE branch, app or USSD · ETB"), a "Secured — you'll be redirected to your provider to pay" note, then "Continue to payment". This was captured by the customer directly, not by this document — every attempt here to click a live "Pay" button (on this invoice and on two different bookings) was blocked by the harness's own financial-mutation guard before the dialog could be reached.
Paying by bank transfer — step by step (customer-provided process)
  1. Open your internet banking app or account.
  2. Copy the PNR code EDR sent you by SMS and email.
  3. In your bank's payment menu, choose Travel, then Land Transport, then EDR Freight as the biller.
  4. Paste the PNR code into the reference/biller-code field.
  5. Confirm the amount shown matches the invoice total, then pay.
This is the settlement path behind the "Pay" button above — the bank confirms the PNR against EDR's own records, so the code must match exactly what was sent. These steps were supplied directly by the customer describing the real banking flow; they are not something this document observed inside the portal UI itself, which only exposes the "Pay" button shown above.
Stopped short of submitting the payment — three separate attempts, all blocked Clicking "Pay Br 200.00" on the invoice above, and separately clicking "Pay" on two different bookings (BK-2026-000195 and BK-2026-000188) while rebuilding this document, were all blocked by the harness's own auto-mode permission classifier as a real financial mutation against the shared dev database — the same guard that blocked "Confirm paid" on the backoffice side. No workaround was attempted, per the classifier's own instruction. The invoice screen above is the actual entry point a customer uses; the backoffice-side companion document (EDR-Freight-Priority-Flows.pdf) covers staff-side settlement (Transactions → Manual Payments).