Control center
Bonded operations walkthrough
Bonded operations provide a bonded-workflow overview and entry points for movement of goods under customs control. This walkthrough route group does not itself call a tRPC query; the WMS bonded router is the backend domain surface, so verify the linked operational screen before assuming an action is persisted.
Key routes
- Bonded overview
Entry point for bonded-zone operations.
- Bonded workflow
Explore the workflow graph used to explain bonded operational stages.
- WMS bonded ledger
Open the warehouse bonded-ledger route.
- WMS movement
Review warehouse movement flows.
Prerequisites and seed data
- Sign in with a tenant-scoped account and use the tenant whose bonded inventory and movement records you intend to review.
- Seed bonded inventory, zone and movement records through their supported operational flows to see populated results.
- The applicable customs/bond controls are organization-specific; follow your approved procedure rather than treating this page as a legal instruction.
Primary workflows
Review bonded operations
Start with the bonded overview, then move to the ledger for recorded inventory activity.
- Open the bonded overview and identify the operation you need to trace. Bonded overview
- Open the WMS bonded ledger to inspect available bonded records. WMS bonded ledger
- Use the movement route to follow an inventory transition. WMS movement
Understand the bonded process flow
Use the workflow explorer as an explanation of process relationships, not a substitute for an official customs filing.
- Open the bonded workflow graph and follow the displayed nodes and links. Bonded workflow
- Return to the WMS ledger to verify actual recorded stock activity. WMS bonded ledger
Concepts
- Bonded goods
- Goods held under customs control subject to the applicable zone and movement rules.
- Bonded ledger
- The WMS route family for bonded inventory and ledger activity.
- Movement event
- A recorded transition of goods between locations or operational states; use the ledger and movement screens to investigate it.
Data sources and implementation status
- The WMS backend mounts a wms.bonded router in backend/src/trpc/trpc.router.ts.
- The /bonded and /bonded-workflow route files do not issue direct tRPC queries; use /wms/bonded for the WMS data surface.
- No specific bonded database model is claimed here; inspect prisma/schema.prisma and the bonded router when investigating persistence.
Permissions
- The API context can include user and tenant values from a bearer token, but guards are applied per procedure. The bonded route page itself has no direct query.
- The shared createCrudRouter filters by ctx.tenantId when present but does not itself require authentication or a non-null tenant; verify the particular WMS procedure before relying on isolation.
- GlobalRole values are defined in prisma/schema.prisma. No bonded-specific role matrix is encoded in this walkthrough.
- Do not release, transfer, or otherwise act on bonded goods without the organization’s authorized operator and customs controls.
Troubleshooting
| Symptom | Check | Where to look |
|---|---|---|
| The bonded overview does not show a live record count. | The overview route has no direct tRPC query; use the WMS bonded ledger and verify that records exist. | app/(app)/bonded/page.tsx and app/(app)/wms/bonded/ |
| WMS bonded requests are forbidden. | Confirm the request has a valid bearer token and tenant context, and check any procedure role requirements. | backend/src/trpc/trpc.context.ts and backend/src/wms/bonded/ |
Where things live
- Bonded overview
- app/(app)/bonded/page.tsx
- Bonded workflow screen
- app/(app)/bonded/bonded-workflow/page.tsx
- WMS bonded routes
- app/(app)/wms/bonded/
- WMS bonded backend router
- backend/src/wms/bonded/
- Backend tRPC router registration
- backend/src/trpc/trpc.router.ts
Audience: operator · Last reviewed: