These are the known limitations of the iPaaS.com Orderful integration. They are inherent to the current design of the integration and to the capabilities of the Orderful EDI transaction API, and they apply to all subscribers. Each limitation is described in plain language along with what it means for you and any recommended action.

Inbound transfers (purchase orders, acknowledgements, invoices, and ship-notice tracking flowing from Orderful into iPaaS.com) are detected by polling. Orderful's transaction API is built around retrieval rather than push notifications, so the integration checks Orderful for new and changed transactions on a schedule.

What this means for you: Set the poll cadence (or trigger an on-demand poll) from Dashboard / Integration Monitoring / Events. New documents appear in iPaaS.com on the next poll rather than instantly. You can also bring in a specific record at any time with Manual Sync using its Orderful transaction ID.

The integration does not perform an automatic bulk import of existing Orderful history when first connected.

What this means for you: Records transfer going forward on the polling schedule, and you can pull any individual record on demand with Manual Sync. To load a larger historical set at onboarding, use the supported bulk sync using Postman workflow.

Shipping methods are created or updated in iPaaS.com when a carrier is encountered while an inbound ship notice/manifest (856) is processed. This collection does not run on its own schedule.

What this means for you: You do not need to configure a separate trigger for shipping methods — they are kept current as tracking is processed. You can also create or refresh one on demand with Manual Sync using the carrier identification code (for example, Ground, Air, or Ocean).

When ship-notice tracking (856) is brought into iPaaS.com, the integration links it to the originating transaction using the Transaction Tracking Match Method subscription setting: by purchase order number (the default), by shipment identification, or by a fallback that tries the purchase order number first and then shipment identification.

What this means for you: The tracking transfer can only succeed if the value it matches on is present and matches an existing transaction. If the purchase order number (or shipment identification, depending on your setting) is missing or does not correspond to a transaction in iPaaS.com, the tracking transfer reports an error. Ensure the matching field is populated on your transactions, and choose the match method that fits how your trading partners populate the ship notice.

The integration creates and updates records in Orderful; it does not delete records in Orderful in response to a deletion in iPaaS.com. Delete mappings are not included in the default templates.

What this means for you: Removing a record in iPaaS.com will not remove the corresponding document in Orderful. Manage cancellations through the appropriate transaction status or document type rather than expecting a delete to propagate.

Orderful EDI documents do not carry an email address, so inbound transactions are created with a placeholder email value.

What this means for you: If your workflow needs a real email address on the transaction, replace the placeholder in the relevant mapping (see the Placeholder Values section below) with a real address or a mapping to a source field that carries one.

Outbound invoices (invoices sent from iPaaS.com to Orderful) carry a currency code that ships set to USD.

What this means for you: If you invoice in a currency other than USD, update the currency mapping before going live (see the Placeholder Values section below).

Outbound documents carry an Orderful stream value that determines which Orderful environment the document is created on (TEST or LIVE).

What this means for you: Set the stream to match your target environment before going live. Sending to the wrong stream routes the document to the wrong Orderful environment. If you are unsure, confirm the correct stream with your trading partner or your MiSP (Managed Integration Service Provider) before enabling outbound transfers.

Several mappings ship with example or default values that each subscriber should review and replace during implementation. These correspond to the inline Placeholder value — replace during implementation: notes on the individual mappings.

This document covers eight known limitations plus the placeholder values to review before go-live. For detailed, per-collection behavior, see the individual Orderful mapping collection descriptions in iPaaS.com.