Overview
Labs plan and execute sample collection from B2B organization sites—stops, routes, and logistics trips
👤 Utsav Katiyar📅 Updated: Apr 7, 2026🏷️ feature
B2B Collection
B2B Collection is how a lab plans and runs sample collection at organization (B2B client) sites: defining pickup locations (stops), building routes across those sites, and scheduling logistics trips so pickup staff visit clients in order—with maps, status, and trail data for operations.
Documentation scope
These pages document B2B organization-site logistics only—stops, routes,
and trips under b2b-logistics. Other lab workflows and products are out
of scope here.
What it is for
- Organization sites as stops — Register client locations (addresses, contacts) where the lab collects samples.
- Routes — Order those stops into efficient paths for recurring or planned use.
- Trips — Assign pickup partners (lab field staff), schedule run times, track progress stop-by-stop, cancel or adjust series, and view trail data for audit and maps.
- Field tools — Mobile and web APIs under
b2b-logisticspower pickup-person apps and the Registration → B2B Collection screens.
Prerequisites
| Gate | Where it lives | Purpose |
|---|---|---|
b2b_collection | Session / LabFeatures (crelio-app) | Enables Registration → B2B Collection (Route Management & Trip Management) in livehealth-frontend |
The sidebar entry B2B Collection appears when isB2bCollectionEnabled() is true (session.b2b_collection).
How the pieces fit together
Related repositories
| Repository | Role |
|---|---|
| livehealth-frontend | Registration → B2B Collection: Route Management & Trip Management (B2bCollection/) |
| crelio-app | Trip management module: B2BTrip, api-v3/trip-management/b2b-logistics/…, locations, routes, visiting persons |
Documentation map
- Workflow guide — Stops → routes → trips → monitoring
- Frontend —
livehealth-frontendsurfaces and APIs used by the UI - Backend — Trip models and URL patterns
- Design decisions — Why
b2b-logisticsdiffers from other trip types