Open Admin → Integrations → DispatchTrack using the Truck icon. This screen saves one tenant-level connection unless a location-specific connection is opened by another supported workflow. CentriPOS remains the fulfillment source of truth; the current customer-visible setup does not contain field-mapping, service-mapping, truck, driver, route-status, or proof-of-delivery controls.

Before you beginUse an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.

Step by step

  1. Go to Admin → Integrations → DispatchTrack. The status badge reads Checking while CentriPOS loads, then Not connected when no settings exist, Saved when credentials are stored but not verified, or Connected after a successful connection test.
  2. Get the Planner API base URL, API key name, API key secret, and—when inbound delivery updates are being configured—the shared webhook token from the authorized DispatchTrack account administrator. Do not paste credentials into a support ticket or screenshot.
  3. Enter Planner API base URL. The example format is https://planner-youraccount.dispatchtrack.com/external_api; use the exact account URL supplied by DispatchTrack rather than copying the placeholder.
  4. Enter API key name and API key secret. All three connection fields—base URL, key name, and key secret—must contain values before Save connection is enabled. The secret field is masked.
  5. Enter Webhook token only when the DispatchTrack webhook has been configured to send the same shared header token to the branded CentriPOS webhook endpoint. The field is masked and is not required merely to enable Save connection.
  6. Choose whether to enable Auto-export eligible local deliveries. The screen explains that manual export remains available from fulfillment. Enable automatic export only after the controlled manual workflow has been proven for this tenant.
  7. Choose Save connection. Saving encrypts the API key name and secret and stores only credential previews for the browser. A successful save reports DispatchTrack settings saved and changes the badge from Not connected to Saved until the connection is verified.
  8. After a save, read Saved key and Updated to confirm which key name is represented and when the settings last changed. CentriPOS does not display the stored key secret or webhook token again.
  9. Choose Test connection. This control is disabled until settings exist. CentriPOS uses the saved credentials to request the DispatchTrack places endpoint; success reports DispatchTrack connection verified and changes the status to Connected. A failure leaves the connection unverified and shows the returned safe error message.
  10. Open Sales → Fulfillment Center and select the Delivery route for a date containing an eligible local-delivery sale. When DispatchTrack is connected, the route area shows DispatchTrack connected and each delivery stop exposes a DispatchTrack button with the External Link icon.
  11. For the first test, choose DispatchTrack on exactly one controlled delivery stop. CentriPOS groups that sale’s active local-delivery fulfillment lines, requires a customer delivery address, and sends the sale as one DispatchTrack stop group. Success reports Delivery sent to DispatchTrack.
  12. Confirm the correct customer name, phone, delivery address, sale reference, fulfillment items, quantities, and delivery instructions in the authorized DispatchTrack account. Do not repeat the export because the external screen is slow; the export uses the sale as an idempotent reference, and any failure is recorded for investigation.
  13. Continue to manage the sale, line-item fulfillment status, cancellations, returns, and customer record in CentriPOS. DispatchTrack supplies external planning and delivery execution; it does not replace the CentriPOS receipt or fulfillment record.
  14. If Test connection fails, first recheck the full account-specific base URL and whether the key name and secret belong together. Save the corrected credentials before testing again. If delivery export fails after a healthy test, verify that the sale is a local delivery, still has active fulfillment lines, and has a complete delivery address; then give support the safe sale number and exact error text, never the credentials.
  15. If the connection should be rotated, enter the complete new base URL, key name, key secret, and applicable webhook token, save once, and test once. There is currently no Disconnect button on this screen, so contact CentriPOS support when the integration must be disabled or removed rather than entering dummy credentials.

Screen and contract reference

Control or areaWhat it means
Truck iconThe exact CentriPOS navigation and page icon for DispatchTrack.
Status badgeChecking, Not connected, Saved, or Connected according to the stored settings and most recent successful verification.
Planner API base URLAccount-specific DispatchTrack external API root; the visible URL is an example, not a universal endpoint.
API key nameName paired with the authorized DispatchTrack API secret. After saving, its preview appears as Saved key.
API key secretMasked DispatchTrack credential. It is encrypted when saved and is not returned to the browser.
Webhook tokenOptional masked shared token used to authenticate configured inbound DispatchTrack webhooks. It is not the API key secret.
Auto-export eligible local deliveriesWhen enabled, marks the connection for automatic export behavior; manual export remains available from fulfillment. Prove manual export first.
Save connectionEnabled only when base URL, key name, and key secret are present. It stores credentials and connection flags but does not by itself prove the remote account is reachable.
Saved key / UpdatedSafe credential-name preview and last settings timestamp; neither reveals the stored secret.
Test connectionUses the saved credentials against the DispatchTrack places endpoint. It is disabled until settings exist.
DispatchTrack connectedFulfillment-route notice shown when the saved connection is verified.
DispatchTrack stop buttonExternal Link action on an eligible delivery stop that sends the sale and its active local-delivery lines to DispatchTrack.
Delivery sent to DispatchTrackSuccessful manual-export confirmation. Verify the external stop before sending anything else.
CentriPOS source of truthSales, fulfillment eligibility and line status, customer context, returns, refunds, and audit history remain in CentriPOS.
Not present on this screenThere are no customer-visible field maps, service maps, driver or truck selectors, route-status maps, proof-of-delivery settings, retry log, or Disconnect button in the current interface.

Expected result

The status badge reads Connected, one controlled local-delivery sale is sent once from Fulfillment Center, and the resulting DispatchTrack stop matches the CentriPOS customer, address, sale reference, fulfillment items, quantities, and instructions without exposing credentials or inventing configuration controls that are not present.

Troubleshooting

  • Confirm you are changing the intended business and location before saving.
  • Record the previous setting when a change affects live selling, payments, tax, or integrations.
  • Use a controlled test record after saving before rolling the setting out broadly.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.