Skip to main content

Order acceptance check

Every 15 minutes this workflow checks new and draft orders for wrong prices, unusual quantities and double orders. An order that needs a look gets an action in the Action Hub.

The action comes up to 15 minutes after the order. The order is not held back in the meantime, unless you set a status for that.

In short
Where you use itIn the background. The results show in the Action Hub
StartsBy itself, every 15 minutes
Changes in PropellerCreates actions. With HOLD_STATUS set it also changes the status of an order
Uses AINo
TextsEnglish and Dutch
Runs in n8nAbout 2,900 a month. That is more than the Starter plan of n8n holds
DifficultyMedium. You check the order statuses and decide who gets the actions

What you get​

One action per order, which names every line that stands out and why. The button opens the order.

An action in the Action Hub for an order with a quantity that is far above what the customer usually orders

CheckAn order is flagged when
PriceA line price differs more than 1% from the price Propeller calculated for this customer or is below the cost price
QuantityA quantity is below the minimum quantity of the product or is 10 times above or below what this customer usually orders
Double orderAn older order of the customer has the same reference in the last 60 days or the same products and quantities in the last 4 hours

What you need​

  • An n8n account with the credential Propeller API key. See Set up n8n.
  • An API key with Viewer access on Order Data and Owner access on User management. To put orders on hold the key needs Editor access on Order Data.
  • An n8n plan with enough runs. See Choose an n8n plan.

How it works​

The workflow reads the orders of the last hour with the status Order or Draft Order. The usual quantity of a product comes from the earlier orders of the same customer and counts after 3 orders with that product.

An order that got an action is never flagged twice.

Good to know

The workflows and agents in the Agent Hub are free to use and adapt. They are examples, not supported product features. Test them in a test environment and check the results before you use them on real customers.

Install it​

Install a workflow from the library explains each step.

  1. Import the file into n8n.
  2. Check that the seven nodes that talk to Propeller use the credential Propeller API key.
  3. Open the Settings node and check CHECK_STATUSES and HISTORY_STATUSES. See Fill in order status codes.
  4. Click Execute workflow to run it once.
  5. Click Publish.

A run only looks at the orders of the last hour, so a test run often finds nothing. To see an action, first place a test order with the reference of an earlier order of the same customer.

Make it yours​

SettingDefaultWhat it does
ASSIGN_TO_ADMIN_USER_IDnullThe colleague who gets all actions. With null each action goes to the account manager of the order
CHECK_STATUSESNEW, DRAFT_ORDERThe statuses of the orders that are checked
HISTORY_STATUSESNEW, CONFIRMED, VALIDATED, ARCHIVEDThe statuses that count as an earlier order of the customer
PRICE_TOLERANCE_PERCENT1How much a line price may differ from the price Propeller calculated
QUANTITY_FACTOR10How many times above or below the usual quantity counts as unusual
HOLD_STATUSnullThe code of a status that an order with an issue gets, for example 'ON_HOLD'

To use HOLD_STATUS, create the status first and allow the change to it from the statuses you check. See Set up order statuses. The action says whether the hold worked.

To run less often, change the node Every 15 Minutes and set LOOKBACK_MINUTES to more than the time between two runs.

Limits​

  • A run checks at most 1,000 new orders.
  • The cost price check is skipped for an order in another currency.