EasyPost integration.

Assign product content, variants, prices, customer identity, stock, and order state to explicit owners. A catalog update and a fulfillment command need different permissions and acceptance tests. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Write-back support is not established for this connection. Review the EasyPost records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

Retain shipment/fulfillment and line IDs, order reference, and carrier context.

Resolve order lines, delivery address, carrier, and any partial-fulfillment references.

Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order. A multi-line purchase retains the correct variant and customer references, while repeated delivery leaves one intended order and fulfillment state.

Estimate the number of Shipment records, the history to load, ongoing changes, and required environments. Include API access, the integration service, destination storage or processing, and the work to maintain mappings and recover from errors. Review current provider pricing against that workload, including any account or API upgrades.