Platform integrators
If you are building an integration for a platform (shipping software, WMS, OMS, multi-merchant SaaS), DashLink supports two distinct integration models.
Model 1 — Each shipper uses their own DashLink account​
Pros​
- Ideal when the platform is not in the payment chain
- Each shipper manages billing directly with DashLink
- Shippers can ingest tracking data outside the platform
- Logs, settings, and configurations stay isolated per merchant
Cons​
- Shippers must manage their own credentials
- Platform engineers need explicit user access to each shipper’s account to view logs/settings
- Complexity increases as number of shippers increases
Model 2 — Integrator has a master account with nested businesses/stores​
Pros​
- Ideal when platform is in the payment chain (reselling DashLink shipping)
- Integrator controls all credentials, account settings, and logs
- Shippers can be completely hands-off
- Easier onboarding for merchants
Cons​
- DashLink cannot filter webhooks or tracking updates by individual shipper
(all events under the master account will be delivered to the webhook endpoint) - Requires careful routing/mapping logic within the platform
Recommendations​
Based on your use case:
| Scenario | Recommended Model |
|---|---|
| You want minimal operational overhead for shippers | Model 2 |
| Shippers need their own billing relationship | Model 1 |
| You need per-shipper webhook isolation | Model 1 |
| You plan to resell shipping | Model 2 |
Important considerations​
- Webhook endpoints receive all parcel events for the account — implement event filtering
- Tracking codes must remain globally unique across all nested shippers
- Store/facility mappings must be maintained in your platform
- Support teams must be able to trace parcel status by business/store identifiers