Exodus Salesforce Docs
Technical Reference

Integrations

External provider, payment, tracking, and Salesforce integration boundaries

3PL Providers

The 3PL runtime integrates with provider systems such as OrderDesk, Packiyo, and Katana. Provider accounts and configs should be managed through Salesforce admin surfaces and provider-account metadata rather than hard-coded credentials.

Provider writeback should update Sales Orders through sync state, tracking, shipped lines, fulfillment history, and runtime request records.

Tracking

AfterShip settings control tracking polling behavior where AfterShip is used. Keep API keys/settings in the runtime settings path, not committed external credential metadata unless the integration is explicitly designed for that credential.

Payments

Payment operations integrate with payment gateways, Authorize.Net-style vault/token flows, hosted/payment link flows, processor events, settlement, and webhooks. Historical tokens and transactions must remain traceable to their execution gateway.

Public Sites and Webhooks

Public checkout and webhook site guest access is modeled through dedicated permission-set groups. Keep those permissions narrow and audit them after changes.

External RMA App

The external RMA app owns signing, photo analysis, inspection, and operational return workflow. Salesforce remains the customer/order correlation system unless a future implementation explicitly changes that boundary.

Last updated on

On this page