Order or catalog
ERP and commerce do not share the same objects or directions.
Connect your tools
Move the right data between Ysend and your systems.
Orders, catalogues, inventory, invoices and statuses use connections designed for each system and purpose.
Start with the need
Start with the data you need to exchange
Invoice or entry
An accounting API and a file export provide different receipts and limitations.
Label or tracking
Check which operations your carrier account supports: rates, labels, cancellation and tracking.
EDI message
Message type fixes direction; transport is configured separately.
Connection details
Open only the details you need
Expand a category to see the data exchanged, setup requirements and connection limitations.
ERP — orders
Sales orders
View connection details
- Direction
- Inbound to Ysend
- Business objects
- Sales orders
- Protocol and version
- ERP-specific API
- Configuration
- Account, endpoint and secrets per connector
- Status
- Customer setup and validation required
- Limitations
- No implied universal or bidirectional ERP sync
Accounting and invoicing
Invoices, credit notes or entries by connector
View connection details
- Direction
- Outbound from Ysend
- Business objects
- Invoices, credit notes or entries by connector
- Protocol and version
- Provider API or file export
- Configuration
- Credentials, target company and connection validation
- Status
- Customer setup and validation required
- Limitations
- Accounting files : No remote delivery or confirmation
Commerce and marketplaces
Catalog, orders, inventory, prices, status
View connection details
- Direction
- Orders inbound; inventory, prices and status outbound
- Business objects
- Catalog, orders, inventory, prices, status
- Protocol and version
- Storefront API, OAuth, keys or tokens by channel
- Configuration
- Store and channel-specific secrets
- Status
- Connection setup and exchange scope depend on the channel
- Limitations
- Legacy write paths not live-verified remain labelled accordingly
EDI and AS2
Orders, ASNs, shipping advice, statuses, acknowledgments
View connection details
- Direction
- Per message and trading partner
- Business objects
- Orders, ASNs, shipping advice, statuses, acknowledgments
- Protocol and version
- X12 004010, PIVOT V14, EANCOM D96A, AS2 RFC 4130
- Configuration
- Separate message profile and partner station
- Status
- Exchange configuration required
- Limitations
- X12 converts the message content; AS2 carries the configured exchange
API, SDK and webhooks
Exposed business resources and events
View connection details
- Direction
- Per resource or event contract
- Business objects
- Exposed business resources and events
- Protocol and version
- REST, versioned TypeScript SDK, webhooks
- Configuration
- Key, scope, subscription and callback URL
- Status
- Developer portal and webhook delivery implemented
- Limitations
- Account rights and the published contract bound each operation
Before activation
Validate the connection in your environment
Check the scope
- data to import and export
- required order or invoice fields
- receipt of a test exchange by the destination system
Prepare the connection
- account, credentials and required permissions
- provider volume and frequency limits
- handling of errors, duplicates and retries
Detailed directories
Open the family that owns your exchange
ERP and accounting
Inbound orders, outbound invoices, protocols, configuration and real status.
Commerce and marketplaces
Authentication, orders, inventory, prices, statuses and channel limitations.
EDI and AS2
Documents, transport receipts and supported recovery.
API and developers
The existing developer portal retains API, SDK, keys and webhooks.
Qualify one exact exchange
Name the object, direction, system, protocol, credentials and expected receipt.