Overview
The first step in the Order Life Cycle is to import orders from external channels.
Orders are imported into Flxpoint via an integrated channel:
- By configuring a Get Orders operation for B2C/sales channels (see Get Orders)
- Automatically through Flxpoint's API for B2B/reseller channels (see Reseller Portal)
As orders are imported, they go through an import workflow, which can dynamically modify data, apply status changes, send custom alerts, etc.
Order Import Workflow
The order import workflow allows you to apply custom rules at the time an order is imported into the system.
Some examples of how users may leverage this workflow:
- Hold or cancel orders in certain circumstances (i.e. International, large quantities, etc.)
- Dynamically apply notes or modify other fields on the order
- Send custom alerts, depending on certain criteria
- Add a tag to orders upon import
To learn more about what you can do with workflows, see Workflows.
Order Hold Status
When an order is successfully imported, the order may be placed in a hold status automatically.
| Reasons An Order May Be Placed On Hold |
|---|
| 1. The user has created a specific order importing workflow that will automatically place the order on hold based on certain conditions. |
| 2. The duplicate order protection toggle is enabled |
| 3. At least one of the order line items is in a Not Managed state |
| 4. At least one of the order line items does not have available quantity at the source |
| 5. The source is not enabled in the specific routing group |
| 6. A shipping policy has not been mapped for the order |
| Flxpoint Pro Tip: Orders in a Hold Status |
|
You are unable to generate a fulfillment request manually or via automation if the order is in a hold status. You must first clear the hold status and resolve the issue before a fulfillment request can be generated. |