Home/HighLevel/Features/Ecommerce Store/HighLevel custom shipping carrier integration: how to set up

Funnels, Websites and Forms

HighLevel custom shipping carrier integration: how to set up

In short

A custom shipping carrier integration lets HighLevel ecommerce users connect any carrier with an API, show live rates at checkout, automate shipment creation and push tracking updates back into orders. It requires a marketplace app, a backend service, and credential handling within the platform.

AreaEcommerce Store · Ecommerce Store
Used forOnline apparel retailer, Handmade crafts shop, Furniture store
Setup steps25 steps in 5 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Ecommerce store owners who need rates from carriers not listed in HighLevel, because the integration expands shipping options.
  • Subscription box businesses that ship regularly and want automated label creation and tracking updates inside HighLevel.
  • Wholesale distributors requiring real time freight pricing and automatic order fulfillment without manual entry.

02Custom shipping carrier integrations, explained

The integration works as a marketplace app that registers a new shipping carrier inside HighLevel. During checkout HighLevel calls a callback URL you provide, receives live rates from your carrier’s API, and shows them to the buyer. After an order is placed, HighLevel sends webhooks that your backend uses to create shipments with the carrier and store the carrier’s order ID.

All configuration lives in the HighLevel app settings and a custom page where users enter their carrier credentials. The backend stores OAuth tokens, carrier keys, and maps HighLevel order IDs to carrier shipment IDs. Fulfillment records with tracking numbers are created in HighLevel via its API, keeping customers informed within the platform.

03How businesses use custom shipping carrier integrations

  • Online apparel retailer. The retailer installs the custom carrier app, adds their regional carrier API keys on a custom page, and enables live rates. When a shopper checks out, HighLevel fetches current shipping costs from the carrier and displays them right away.
  • Handmade crafts shop. The shop owner saves their preferred carrier credentials through the embedded custom page. As orders complete, the backend creates shipments with the carrier automatically and records tracking numbers in HighLevel.
  • Furniture store. The store receives carrier webhook notifications for tracking updates, matches them to the corresponding HighLevel order, and triggers a fulfillment record so customers receive shipping notifications.

04The numbers and rules that matter

  • Create shipping rate placeholder amount: 0.

05Before you start

  • A backend service that can handle OAuth redirects, HighLevel webhooks and carrier webhooks.
  • A database to store OAuth tokens, carrier credentials and order mappings securely.
  • Basic knowledge of REST APIs and OAuth 2.0 authorization flow.

06How to set up and use custom shipping carrier integrations in HighLevel

Initial setup

  1. Open the HighLevel Marketplace developer portal and start a new app.
  2. Select Subaccount as the app type.
  3. Enter the OAuth redirect URI that points to your backend endpoint.
  4. Provide the webhook URL that will receive HighLevel events.
  5. Enable OrderCreate and OrderStatusUpdate webhook types.
  6. Add the required scopes: orders.readonly, orders.write, shipping.readonly, shipping.write.

Frontend UI configuration

  1. Create a custom page that collects the carrier API key, secret and account ID.
  2. Add the page to HighLevel via a custom menu link and retrieve the location context token.
  3. Send the entered credentials to your backend, validate them with the carrier, and store them linked to the locationId.

Live shipping rates implementation

  1. Call the HighLevel API to create a shipping carrier record, supplying the carrier name and callbackUrl.
  2. Confirm that the callbackUrl points to an endpoint that can accept POST requests at the /rates path, because HighLevel will append /rates.
  3. Save the returned shippingCarrierId for later use.
  4. Deploy an endpoint at the callbackUrl that accepts POST requests for live rate calculations.
  5. Translate the incoming rate request to the carrier’s API format, request rates, and return them in HighLevel’s response structure.
  6. Add a carrier rate to each relevant shipping zone via the HighLevel API, marking it as a carrier rate with a placeholder amount of zero.

Order syncing and fulfillment

  1. Enable OrderCreate and OrderStatusUpdate webhooks in the app configuration, pointing to your HighLevel webhook listener.
  2. When a webhook arrives, verify the payload signature (important for security) and confirm the order status is completed.
  3. Retrieve the full order details from the HighLevel API.
  4. Use the stored carrier credentials to create a shipment with the carrier API and record the carrier shipment ID.
  5. Validate carrier webhook authenticity when notifications arrive, match them to the HighLevel order using the stored mapping, and extract tracking information.
  6. Send a fulfillment request to HighLevel that includes the tracking number, carrier name and notification preference.

Disconnection and uninstallation

  1. Listen for the App Uninstalled webhook from HighLevel.
  2. When received, look up the shippingCarrierId associated with the location.
  3. Delete the shipping carrier record via the HighLevel DELETE /shipping carrier endpoint.
  4. Remove stored carrier credentials and any registered carrier webhooks from your system.

07What it looks like in HighLevel

08Settings that matter

  • App Type. Determines whether the app can be installed on individual location accounts; set to Subaccount.
  • Redirect URI. The URL where HighLevel sends the OAuth callback after a user authorizes the app.
  • Webhook URL. The endpoint that receives HighLevel event webhooks such as OrderCreate and OrderStatusUpdate.
  • Required Scopes. Permissions the app needs to read and write orders and shipping data; includes orders.readonly, orders.write, shipping.readonly, shipping.write.
  • isCarrierRate. Flags a shipping zone rate as a live carrier rate, causing HighLevel to request rates from the callback URL.

09Things to know before you rely on it

  • The callbackUrl must point to an endpoint that can accept POST requests at the /rates path.
  • Carrier rates added to zones use a placeholder amount of zero because the actual cost is fetched live.
  • All credential data must be stored securely; the integration does not handle encryption automatically.
  • The integration requires custom backend development; no built in HighLevel UI replaces these steps.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

I find that building a custom carrier integration extends HighLevel's ecommerce capabilities, but it adds complexity around OAuth authentication, webhook handling, and secure data storage.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about custom shipping carrier integrations.

How do I create a marketplace app for a custom carrier?

Open the HighLevel Marketplace developer portal, start a new app, choose Subaccount as the app type, set a redirect URI and webhook URL, enable OrderCreate and OrderStatusUpdate webhooks, and save the app.

Which scopes are required for a shipping carrier integration?

The app must request orders.readonly, orders.write, shipping.readonly and shipping.write so it can read and modify orders and shipping data.

How does HighLevel obtain live shipping rates from my carrier?

HighLevel calls the callbackUrl you register when a shopper checks out. Your endpoint receives the cart and destination details, queries the carrier API for rates, and returns them in the format HighLevel expects.

What happens after a carrier provides a tracking number?

Your backend receives a carrier webhook, matches the carrier shipment ID to the HighLevel order, and sends a fulfillment request to HighLevel that includes the tracking number and carrier name.

How can I remove my custom carrier from a location?

Listen for the App Uninstalled webhook, locate the shippingCarrierId for the affected location, and issue a DELETE request to the HighLevel /shipping carrier endpoint. Then clean up any stored credentials.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.