Configure organization stops, routes, and logistics trips for B2B sample collection

Workflow Guide

This page covers the B2B Collection workflow: organization sites → routes → trips → monitoring.

1. Enable access

Ensure the lab has b2b_collection enabled so Registration → B2B Collection appears for logistics staff.

Navigate to Registration → B2B Collection → Route Management.

Create stops — named locations (typically B2B client / organization sites) with address, coordinates, and contact details.
Stops are stored via trip-management APIs: api-v3/trip-management/b2b-logistics/location/… and reused across routes.

Organizations

Stops can be linked to an organization record where the product supports it, so routes reflect real client sites.

Under Route Management:

Create a route: an ordered list of stops with segment distances.
Edit, copy, or disable routes from the grid (soft-disable via PATCH where applicable).

A route is a reusable path template; execution happens when you schedule a trip.

Navigate to Registration → B2B Collection → Trip Management.

Filter by date range and optional trip status (pending, in progress, completed, cancelled, etc.).
Create trip — choose a pickup partner, schedule the run, and attach ordered trip locations (stops).
Recurring / series — multiple scheduled instances use POST …/trips/new/bulk when the UI sends scheduled_trips.
Edit or cancel — single occurrence vs whole series (update vs update/bulk).

Pickup partners come from api-v3/trip-management/b2b-logistics/pickup-persons/list.

Open Trip details from the list (URL includes tripId and date range for context).
Review per-stop status, comments, and any sample summaries returned by the API.
Trail — GET …/trips/{tripId}/{pickupPersonId}/trail for path history and maps.