LOADME · MULTI SITE DISTRIBUTION

Keep dispatch across sites easier to follow

Discuss how site responsibilities, recurring deliveries and reporting should be configured for your operation.

Conceptual illustration.

Identify each site and team

Describe who creates orders, allocates transport and reviews delivery evidence at each location. This defines the organisational model to validate.

Follow recurring routes and shipments

Use the relevant route and shipment records to coordinate activity. Agree how responsibilities move between sites and external participants.

Illustrative workflow. Example participants. Permitted records and actions are agreed during setup; this is not a permissions specification.

  • Office team
  • Drivers
  • Customers

Example participants. Permitted records and actions are agreed during setup; this is not a permissions specification.

Agree the review view

Cross-site permissions and reporting depend on tenant structure. Demonstrate the required access and report scope before rollout.

Practical questions

Are cross-site views automatic?

Cross-site access and reporting must be checked against tenant structure.

Where should we begin?

List the sites and the teams responsible for orders, allocation and delivery records.

Can recurring routes be reviewed?

Yes. Use representative routes and shipments to validate the required operating model.

Start with your transport workflow

Tell us what you move, who is involved and which task you want to improve. We will discuss the relevant setup and any optional work.