Send approved orders to the right destination.
Poppelo has connectors for QuickBooks Online, Shopify, and NetSuite. Intake collects the customer document; destination delivery creates the supported record after approval.
Intake and delivery solve different problems
Email, upload, SFTP, and API intake bring documents into the review workflow. A destination connector takes the approved record out to your accounting or order system. Connecting an inbox does not also connect a destination, and extracting an order does not confirm that it was delivered.
Choose the record your destination supports
QuickBooks Online receives customer orders as Estimates, Shopify receives draft orders, and the NetSuite implementation supports sales-order delivery. Routing to one storefront among connected storefronts is implemented, with storefront and routing-rule plan limits. Fan-out sends the same approved order to a storefront plus an accounting destination and requires an additional plan entitlement. Both depend on rollout: production integration startup requires DESTINATIONS_V2_CLAIMS=true, and deployment flags remain unverified. Confirm enablement and destination acceptance with Poppelo before relying on either workflow.
Check mappings and acceptance before rollout
Connector implementations exist, but actual provider acceptance and certified currency, discount, charge, and amendment mappings remain open in the capability ledger. Unsupported financial mappings and revisions require manual handling. SAP Business One and Dynamics 365 are planned, rather than included as supported connectors here.
Questions about this workflow
Does a connector support every record type in that system?
No. Each connector has a supported record type and mapping boundaries. Confirm your workflow and financial mappings before rollout.