Introduction
This guide explains how to request and set up a new courier or 3PL integration for order fulfillment in salesorder's helpdesk. It covers the information we need, what happens during configuration, and how we validate the workflow before go-live.
Prerequisites
Before you submit a request, please confirm the provider details and the fulfillment functions you want enabled. This helps us assess whether the integration can be configured through an existing connector, API, or custom integration path.
- Provider name and service type
- Required capabilities such as shipping rates, label creation, tracking updates, or order status syncing
- Account credentials or access details
- API documentation, if available
- Test environment details, sandbox credentials, or webhook endpoints, if applicable
Step-by-step instructions
Step 1: Confirm the integration requirements
Identify the courier or 3PL provider and specify exactly what you need the integration to do. For example, you may need rate shopping, shipment booking, label generation, tracking events, delivery updates, or fulfillment status syncing back to your order management workflow.
Step 2: Gather the required access details
Send the credentials, API keys, usernames, passwords, or token-based access details needed to connect the provider. If the provider uses a sandbox or staging environment, include those details as well so we can test safely before production setup.
Step 3: Share the provider documentation
Provide any available API documentation, integration guides, rate limits, authentication requirements, and webhook specifications. If there are field mappings or shipping rules that must be followed, include those instructions too.
Step 4: Submit the request to support
Open a support request and include the provider name, required services, credentials, documentation, and test environment details. The more complete your request is, the faster we can review the setup and confirm the best implementation path.
Step 5: Review the configuration approach
We will review the integration requirements and determine whether the provider is already supported, can be configured through an existing connection, or requires a custom integration. If additional information is needed, we will contact you before proceeding.
Step 6: Test the workflow
After configuration, we will test the end-to-end workflow to confirm that orders, labels, tracking information, and status updates are passing correctly between systems. If issues are found, we will adjust the mapping or connection settings and retest.
Step 7: Confirm go-live readiness
Once testing is successful, we will confirm the integration is ready for production use. If needed, we can also advise on monitoring, exception handling, and operational checks after launch.
Tips and best practices
- Include the exact provider name and account type to avoid setup delays.
- Specify which fulfillment functions are required so we can configure only what you need.
- Share test credentials early to speed up validation.
- Provide sample orders or test scenarios if your workflow has special routing or shipping rules.
- Confirm whether you need one-way or two-way syncing for order and tracking updates.
If the provider is not supported
If the courier or 3PL is not already supported, we can advise on the best available alternative or a custom integration path. In some cases, this may involve API-based development, middleware, or a different supported provider that meets your operational requirements.
Next steps
To get started, submit your integration request with the provider details, required services, credentials, documentation, and test environment information. If you are unsure what to include, contact support and we will help you prepare the request.
Additional information
For faster resolution, include any known constraints such as label formats, shipping account rules, warehouse-specific requirements, or marketplace fulfillment dependencies. This helps us ensure the integration supports your order lifecycle accurately from shipment creation through tracking updates.
Comments
0 comments
Please sign in to leave a comment.