Review incoming distributor orders before routing them downstream.
Poppelo brings emailed and scanned customer purchase orders into a structured workflow with exception review and operational history. Destination routing is implemented but depends on verified rollout and plan entitlements.
Capture orders across document quality levels
Email attachments and manual uploads can include PDFs, spreadsheets, scans, and photos. Extraction prepares fields and line items for validation. A poor scan, conflicting customer reference, or missing quantity should remain visible for a reviewer rather than be treated as a safe assumption.
Verify the intended routing workflow
Routing to one storefront among connected storefronts is implemented, with storefront and routing-rule plan limits. Fan-out writes the same order to a storefront plus an accounting destination and requires an additional plan entitlement. Production integration startup requires DESTINATIONS_V2_CLAIMS=true, and deployment flags remain unverified. Confirm rollout and destination acceptance with Poppelo before relying on these workflows. If another system already syncs orders downstream, establish the intended write path to prevent duplicate records from separate workflows.
Trace approval separately from delivery
The review decision, dispatch, and destination result are different stages. Audit history helps an operator follow the handoff. An uncertain write requires reconciliation evidence before a retry; unsupported financial mappings and revisions remain manual cases. Confirm connector acceptance for the destination account before rollout.
Questions about this workflow
Can orders go to different connected storefronts?
Routing to one storefront is implemented but depends on verified rollout and plan limits. Fan-out to a storefront plus an accounting destination also requires an additional plan entitlement. Confirm enablement and destination acceptance with Poppelo before relying on either workflow.