Playbook

Standalone Booking Desk for Partner Ops (Standalone Booking Desk For Partner Ops)

Standalone Booking Desk for Partner Ops — a production lesson from logistics operations platforms.

Partner Ferry Booking Desk

Part 7 of 8

A series on managing ferry partner capacity through ticket lifecycles and discount workflows.

Partner ferry booking diagram

Standalone Booking Desk for Partner Ops

Partner operators may need a dedicated desk URL while still consuming the shared auth remote.

same remote, own origin, auth remote shared

Aynı remote, iki teslimat kanalı.

Concepts, defined where they first appear

📦 Partner Capacity
Ferry partner voyage/capacity truth — not a flat CRUD row.

📦 Ticket Lifecycle
Transitions such as sold → used → canceled.

📦 Discount Workflow
Calculate / approve / revert steps with authority gates.

📦 Booking Desk
Surface where partner ops manage tickets and vehicle context.

Teams that blur these concepts confuse UI state with integration truth.

Shape of the problem

Partner operators may need a dedicated desk URL while still consuming the shared auth remote.

same remote, own origin, auth remote shared

The split that works

Aynı remote, iki teslimat kanalı.

same remote, own origin, auth remote shared
        ↓
   explicit contract

Where production breaks

Incidents grow when radius, identity, or deploy assumptions stay implicit. Make the contract visible and reversible.

The mappings that get confused most often

❌ One app is always safer
✓ Without clear boundaries, one app is more fragile

❌ Keep config hardcoded
✓ Radius, remote URLs, and expose paths are operational contracts

❌ Vendor/API truth is UI state
✓ Vendor feed is evidence; ops state is a decision

A checklist for auditing your own system

  1. Write the ownership boundary for this surface in one sentence.
  2. If this contract changes, who deploys?
  3. On timeout or vendor delay, what does the UI show?
  4. Do you test embedded and standalone paths separately?
  5. Deny-list check: any vendor/domain leakage in copy?

What to take away from this part

  1. Contracts must be visible: expose paths, radius, ticket state, or remote URLs.
  2. The gap between UI and external systems is a design choice, not a bug.
  3. Independent deploy means independent rollback.

The boundary you hide will find you in production.

FAQ

Frequently asked questions

What is Partner Capacity?

Ferry partner voyage/capacity truth — not a flat CRUD row.

What is Ticket Lifecycle?

Transitions such as sold → used → canceled.

Is it true that "One app is always safer"?

Without clear boundaries, one app is more fragile

What does this part lock in?

Aynı remote, iki teslimat kanalı. Partner operators may need a dedicated desk URL while still consuming the shared auth remote.

Engineering Principles Learned

  • Ownership and release boundaries are as real as the domain model.
  • External systems produce evidence; operational state is decided by you.
  • Version the contract; keep internals free to move.

Continue reading

Continue reading

Next in series

Next in series

Same series

Paylaş