Skip to main content

Delivery services overview

Use Delivery Services in Connect to understand the source-defined system delivery-company inventory. Opening the page starts authenticated reads for delivery companies, businesses, and payment methods; do not open it as a documentation or support probe.

Availability

The /connect/delivery-services route is limited to level-0 administrators. It requires either Enterprise with Connect delivery services enabled or Pro with the Pro Connect feature enabled; otherwise source redirects to Home. The Connect sidebar parent separately excludes read-only administrator, delivery-manager, and business-owner classifications.

Open Delivery Services

  1. In the Dashboard sidebar, select Connect.
  2. Select Delivery services.
  3. Use Search or the page controls to find a listed service.

Current source requests driver-company records whose owner type is system, plus related driver-group and plugin state. The table defines ID, Delivery Company, Connect to, and Actions columns. Search and pagination operate on the list already returned to the client.

Understand connection states

Each provider can be in a different state:

  • Installed means the returned delivery-company record has a plugin identifier.
  • Install is a source-defined write control shown when that identifier is absent. Some eligible Pro states instead show a contact-us control.
  • A service with an installed plugin can still be unavailable for configuration if it has no linked delivery driver group or the linked group cannot be loaded.
  • The enabled switch is wired to a delivery-company update request. Treat it as an operational write, not an informational label.

The source tree is not a support matrix. Only an admitted project response could determine which records exist, and no runtime inventory was requested or captured for this guide.

Current client source passes the currently selected detail identifier—not the identifier of the row that owns the switch—to the update handler. Before a detail is selected this value is null, and after selection it can refer to another row. Do not use the switch as a diagnostic or assume it targets the displayed row; treat this as an unresolved client-source targeting risk.

Review a service safely

Selecting an installed row first issues an authenticated driver-group read. If its plugin or linked group is absent, source keeps the detail panel closed and shows a prerequisite error. If the group is returned, opening the panel can trigger an additional configuration read and expose operational associations.

Sensitive integration data

Provider configuration can include credentials, keys, webhook URLs, account data, business associations, schedules, and delivery-zone information. Do not copy this data into tickets, chat, screenshots, or recordings unless your organization has approved the sharing and redaction process.

Operational actions

Install is wired to a plugin-registration request using the record’s plugin root, followed by a client reload only on the source-reported non-error branch. The enable control is wired to a delivery-company update; current API source can propagate enabled or name changes to a linked driver group. These are source-defined effects, not proof of deployed or successful behavior.

Open Configure a delivery service only when the provider plugin and linked driver group are ready and you have the required credentials and operational approval.

Troubleshooting

Why is Delivery services missing from Connect?

The feature is restricted to administrator accounts and eligible project plans with the required Connect feature enabled. If a direct URL returns you to Home, the route gate is not satisfied.

Why can’t I open a listed service?

Current client source blocks the detail panel when the plugin identifier or linked driver group is missing, or when the group read does not return an identifier. Resolve the prerequisite through an approved administration process; do not install or alter records to test this guide.

Why does a provider not appear in the list?

The page shows the project’s system delivery-service records, not every integration that exists in the product code. Provider availability is project- and configuration-dependent.


Related guides: Configure a delivery service · Delivery overview