These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Food Distribution SCM
- Features
- Delivery points
Delivery points
Keep each venue or destination tied to its operating organization.
OverviewActive Delivery Points×
Food Distribution SCM · Delivery points
New
Active Delivery Points
Delivery points
| Name | Code | Contact name | Address | Eligibility note | Organization | |
|---|---|---|---|---|---|---|
| Point 100 | CDE-664 | Contact 326 | H-20 | EN-611 | ORG-1523 | |
| Point 557 | CDE-448 | Contact 500 | V-20 | EN-965 | ORG-3411 | |
| Point 429 | CDE-866 | Contact 904 | X-14 | EN-464 | ORG-8220 | |
| Point 275 | CDE-329 | Contact 156 | Z-3 | EN-126 | ORG-8167 | |
| Point 716 | CDE-268 | Contact 134 | F-24 | EN-230 | ORG-9555 |
6 of 6 records
Point 100Delivery points · DP-62768
CodeCDE-664
Contact nameContact 326
AddressH-20
Eligibility noteEN-611
OrganizationORG-1523
What you can do
Give each destination an accountable record
A delivery point may be a dining room, outlet, venue or other destination the operation serves. Order Coordinator selects it on an order before accepting the service commitment. Its name and code identify the place; contact and address tell the service team whom and where to serve. The eligibility note lets the team keep an operating instruction near the destination rather than relying on a conversation.
Delivery points belong to an organization. That link matters when several operating organizations share a catalogue or staff population. Admin maintains organization codes, time zones, currencies and active state. Team members also link to their organization and platform identity, giving the operator a basis for assigning order owners and independent reviewers.
How the work is organized
- Destination record. Keep the destination’s name, code, contact, address, eligibility note and active state together.
- Operating organization. Keep the unit responsible for the destination and its time zone visible to staff.
- People. Link the order owner and reviewer to staff records, with their organization and active state.
What to agree during setup
Decide how destination codes are assigned, who maintains addresses, and what an eligibility note must say when a venue has special service instructions. Agree when a destination becomes inactive and who checks open orders before changing it. Confirm the operating organization for each destination and the time zone used when scheduling service.
A new outlet might share a contact with an existing location. It still needs its own code and address so an order can point to the actual destination. If the outlet closes, the team can mark it inactive for new intake while retaining the destination link on earlier orders and distribution events.
Check the handoff on an actual case
Pick a current order and follow its destination reference. Verify the code, address and contact against the team’s dispatch instructions. Check that the operating organization on the order and ticket is the intended one. Then inspect the order owner and the supervisor who will review the ticket. Their identities should lead back to distinct team members for the independent decision.
Before accepting a service time, the coordinator reads the destination eligibility note and planned service scope. A destination record alone does not complete a shipment; the subsequent distribution events record allocation, picking, shipping, delivery or return. This distinction helps staff answer a customer’s question about where the order is in the operation.
What your team sees
- Active Delivery Points — Available destinations with their contact and operating context.
- Open Distribution Orders — Current commitments that name those destinations.
Follow the work through
See order acceptance for the destination check and dispatch review for the reviewed release.
What it keeps track of
Data model- Delivery points
- Dining rooms, outlets, venues and delivery destinations served by the operation.
- Organizations
- Operating organizations within the food and beverage group.
- Team members
- Staff members linked to an organization and platform identity.
- Users
- Users
- Distribution orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Dispatch tickets
- Kitchen tickets submitted for review and release against a meal order.
Who uses it
Permissions- Admin
- Maintains organizations, destinations and staff.
- Order Coordinator
- Chooses the destination for the order.
- Delivery Operator
- Uses its address and contact.
- Dispatch Supervisor
- Checks ticket context before release.
Set up Food Distribution SCM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.