Skip to content
  • There are no suggestions because the search field is empty.

Ella Autonomous Mode

With Autonomous Mode, Ella reads your order inbox, decides on her own whether each purchase order or quote is safe to post, and pushes the safe ones straight to your ERP. You review the order in your ERP, where you already work, and Ella emails you about anything that needs your attention.

This article explains how Ella decides what to push, what you see in your ERP, the emails Ella sends, and how to fix and re-push an order Ella has held.

Platform: Ella      |      Who is this for: Admins, Sales Reps & Operations Teams


Table of Contents


Before You Begin

  • Your AI Order Entry Assistant must already be set up. If it isn't, see AI Order Entry Assistant, Getting Started.
  • Orders must reach Ella by email. You can either connect the Email Connector (Gmail or Outlook) to the inbox where orders arrive, such as your own mailbox or a shared inbox like orders@yourcompany.com, or forward orders to a dedicated email address set up for Ella.
  • Your ERP connector must be set up, including the Ella custom fields in your ERP. Your WizCommerce team creates these with you during onboarding. Autonomous Mode supports every ERP integration that WizOrder supports.
  • Autonomous Mode covers purchase orders and quotes only.

A. What is Autonomous Mode

In review mode, every order Ella processes waits on the review page until someone submits it. A clean 3-line PO takes the same trip as a messy 60-line one.

In Autonomous Mode, Ella does the last step for you. Ella checks every order, posts the safe ones to your ERP, and holds back only the ones that need a person. Everything Ella knows about the order travels with it into the ERP: an order-level verdict, a flag and reason on each line that needs a look, and a link to the original email with all its attachments.

Review Mode Autonomous Mode

Every order waits on Ella's review page

Safe orders post to your ERP automatically

You review and submit in Ella

You review in your ERP, where you already work

Ella's review page is your work queue

Ella's screen is only for fixing held orders

Email confirms the order was processed

Email tells you what was pushed, what was flagged, and what needs your attention.

Two rules shape how Autonomous Mode works:

  • An order is all or nothing by default. Ella never pushes some lines and holds others. If one line has a blocking issue, the whole order is held. This can be configured for your account.
  • Once pushed, Ella never updates the order. Any edits after the push happen in your ERP.

Note: By default, orders land in your ERP's review state (in NetSuite, Pending Approval), so nothing goes live until someone releases it. Posting orders as submitted orders, depending on the customer's POs, is planned for a later release.


B. How Ella Reads Your Inbox

Ella reads every email that arrives in your connected inbox, works out whether it contains a purchase order or a quote, and if it does, pushes it to your ERP. If needed, your WizCommerce team can set up a blocked senders list, so emails from those senders are filtered out before Ella reads them.

» Every Email Gets an Outcome

No email is silently skipped. Each one is marked with one of these outcomes:

Outcome What it means

Processed

Ella found a PO or quote and processed it

No PO found

The email looked like an order, but Ella found no PO or quote in it

Not an order

The email isn't an order, for example a general enquiry

Unclassified

Ella isn't sure. The email waits in the unclassified queue for a quick human look

Failed

Something went wrong while processing. The email goes to a queue, never to a skip

Note: Sometimes one of your customers sends an email with an attachment that doesn't look like an order to Ella. Because this is how a missed PO usually looks, Ella doesn't ignore it. Ella moves the email to the unclassified queue so someone on your team can check it.

» Ella Replies to Every Sender

Ella replies to each email so the sender knows where things stand:

  • Order found: Ella confirms the order is being processed.
  • No order found: Ella lets the sender know, and asks them to reply on the same thread if the email does contain an order.

If the sender replies on that thread, the email goes back into Ella's queue for another look. This way, your customer also helps catch anything Ella may have missed.

Note: This only works when orders come in through the Email Connector. You can also reply to Ella's email with corrections, and Ella will make the changes.


C. How Ella Decides: Push, Push with Warnings, or Hold

For every order, Ella runs a set of checks and lands on one of three outcomes. There is no score or percentage in Autonomous Mode. Each check simply passes or fails.

Outcome When it happens What Ella does

Push, confident

Every check passed

Posts the order to your ERP with the verdict Ella - Confident and sends a success email

Push, with warnings

All critical checks passed, but some lines need a look

Posts the order with flags on the affected lines and the verdict Ella - Review advised, and sends a warning email

Hold

A critical check failed, a hold rule applied, or there were too many warnings

Creates nothing in your ERP, not even a draft. Sends an email explaining why, with a link to fix and re-push in Ella

» Errors, Warnings, and Notes

Every issue Ella finds is one of three types. Which issues count as errors, warnings, or notes can be configured for your account.

  • Error: Blocks the order. Ella holds it and tells you why. Errors are facts, for example a product that doesn't exist in your catalog.
  • Warning: Doesn't block the order. Ella pushes it and flags the line in your ERP, for example a price that differs from your system price.
  • Note: For your information only, for example a delivery instruction on the PO. Notes never change the verdict and don't trigger an email.

Note: Ella never edits a value to fix a warning. The quantity and price on the PO are what get pushed. Ella adds a flag and a reason to the line so you can decide.

» What Holds an Order
Issue Example message

Customer not found

Couldn't match "Whitfield & Sons Furniture" to a customer in NetSuite. Closest on file: Whitfield Furniture Co.

Duplicate PO number

PO #4482 was already processed on Aug 12 as SO-1041.

Required field missing

No ship-to address on the PO, and none on file for this customer.

Value not a configured option

Ship method "Overnight Freight" isn't one of the configured options for this field.

SKU not matched

Line 7: "BLK-TBL-36R" didn't match any SKU. Closest: BLK-TBL-36S.

Line math doesn't add up

Line 3: 12 x $18.50 = $222.00, but the PO shows $261.00.

Order total above your limit

Order total $32,400 is above the $25,000 auto-push limit. Held for review; nothing looks wrong.

Your hold rule applied

Held by your rule: orders from Harbor & Pine always go to review.

The last two are hold rules, not errors. The order isn't wrong; your team has asked to review orders like it. The email says so, so a clean order never reads as broken.

» What Pushes with a Warning
Issue Example message

Price differs from system price

PO price $36.00 vs system price $40.00 for SKU1. Pushed the PO price.

Product out of stock

SKU1 shows out of stock. Pushed as on the PO; adjust fulfilment in the ERP.

Product not on the customer's price list

SKU1 has no price on this customer's price list. Pushed the PO price $36.00. Verify.

Below MOQ or not a multiple of IOQ

Qty 5 is below the MOQ of 10. Pushed as on the PO.

Close second match

Matched SKU1, but SKU1-B was nearly as close. Verify the pick.

Rounding difference

PO line total $359.64 differs from qty x price $360.00. Rounding only.

Ship date already passed

Requested ship date Aug 12 has already passed.

Note: If a field is missing from the PO but Ella can fill it from your customer or product records, the check passes. For example, a PO with no payment terms passes if the customer has payment terms on file.


D. What You See in Your ERP

Every order Ella pushes carries its own review notes, so you never have to go back to Ella to understand it.

» On the Order
Field What it shows

Ella Verdict

Ella - Confident or Ella - Review advised

Areas to Focus

The issues to check first, each starting with its line number. If the list is too long for the field, it ends with "+N more in Ella"

Source Email

A link where you can view the complete original email and all its attachments

Ella Link

A link to the order in Ella, with the Ella order ID

» On Each Line
Field What it shows

Ella Flag

OK, Check - SKU, Check - Qty, Check - Price, Check - Discount, or Info

Ella Reason

Why the line was flagged, for example "PO price $36.00 vs system price $40.00 for SKU1. Pushed the PO price."

Ella Suggestion

Ella's suggested fix, where available

To review an order pushed with warnings:

  1. Open the order in your ERP.
  2. Read the Areas to Focus field to see which lines need a look.
  3. Check each line flagged in the Ella Flag field against its Ella Reason.
  4. Make any changes directly in your ERP.
  5. Approve or release the order as you normally would.

Note: Every attachment on the email travels with the order, including files Ella didn't process, such as artwork or spec sheets.


E. Emails Ella Sends

In Autonomous Mode, email is how Ella tells you what happened and what needs you. Each scenario has its own template.

Email When you get it Who receives it

Success

The order was pushed with no issues. Includes the ERP link and the Ella link

Internal team

Pushed with warnings

The order was pushed, but some lines are flagged. Lists flagged lines, most important first

Internal team only

Held

The order was held. Lists every reason, with a link to fix and re-push in Ella

Internal team only

Push failed

Your ERP rejected the order. Shows the ERP's own error, with a link to fix and re-push

Internal team only

Acknowledgement

Ella received the email: either "processing your order" or "no order found"

Customer, on their original thread

Daily digest

Once a day: counts of orders processed, pushed confident, pushed with warnings, held, and failed, plus emails received but not processed

Internal team

Note: Warning, held, and push-failed emails are never sent to your customer. They can include business details, such as a price difference or a hold rule, that your customer shouldn't see. Only customer-safe messages reply on the customer's thread.

» Who Gets Copied
  • If configured, the sales rep on the customer record is copied on each email. If no rep email is on file, the email still sends without a CC.
  • Your Administrator can add extra recipients for each scenario, for example ops@ on push-failed emails or finance@ on held emails.

F. Fix and Re-push a Held Order

When Ella holds an order, nothing is created in your ERP. You fix it in Ella and push it again.

  1. Open the Held email and click the Ella link. 
  2. The order opens in Ella with every reason it was held listed at the top.
  3. Fix each issue on the order, for example select the correct customer or match the line to the right SKU.
  4. Click Re-push to ERP.
  5. Ella runs her checks again and pushes the order. You receive the matching success or warning email.

» If the order was held by a rule (order total above your limit, or a customer-specific rule):

  1. Open the order in Ella and check it as you normally would. The email will say nothing looks wrong.
  2. Click Re-push to ERP to send it through.

» If the push failed in your ERP:

  1. Open the Push failed email to see the error your ERP returned.
  2. Click the link to open the order in Ella.
  3. Fix the field the ERP rejected and click Re-push to ERP.

Note: You only fix orders in Ella when they are held or failed. Once an order has been pushed, make all further changes in your ERP. Ella doesn't update an order after it has been pushed.


G. Track Activity on the Dashboard

The Ella dashboard shows how Autonomous Mode is performing, and where something needs you.

Metric What it tells you

Emails read

Total emails Ella read from your connected inbox

POs processed

Orders and quotes Ella found and processed

Pushed to ERP

Orders pushed, split into confident and with warnings

Autonomy rate

Share of orders pushed with no human touch

Failed

Orders your ERP rejected

Needs attention

Held orders waiting for someone to fix and re-push

Unclassified queue

Emails waiting for a human look, and the age of the oldest one

Emails not processed

Emails received that Ella didn't turn into an order

Silent error rate

Orders pushed with no human touch that were later corrected in your ERP

Note: To measure the silent error rate, Ella reads each pushed order back from your ERP a few days later and compares it with the original push.


H. Admin Controls

Administrators decide how strict Autonomous Mode is. Only Admins can change these settings, and every change is logged.

Setting What it controls

Order total limit

Orders above this total are held for review, even if nothing is wrong. Your WizCommerce team sets this up for you; it isn't available in your Admin settings.

Required fields

Fields that must be present before Ella pushes an order

Exception rules

Always hold orders by order total, ship-to country, or specific customer

Duplicate PO numbers

Hold (default) or allow a reused PO number, for example for blanket POs. Can be set per customer or customer group

Issue severity

Turn a warning into an error so it holds the order

Submission mode

Post orders to your ERP's review state (default) or as confirmed orders

Email templates and recipients

Edit each email template and choose who receives it

Notes in email

Include notes in emails (off by default)

Note:

  • You can make Ella stricter, but you can't loosen an error into a warning, because errors are facts. The one exception is duplicate PO numbers, since reusing a PO number can be valid for your business.

  • Settings apply across your whole account to start. Separate limits for customer groups and individual customers are coming later. When they arrive, a customer's own setting takes priority over its group, and a group's over your account setting.
» Moving a Customer to Confirmed Orders

When a customer's orders have run cleanly in your ERP's review state for long enough, your Administrator can switch that customer's Submission mode to confirmed orders. Ella's orders for that customer then post as confirmed orders, with no release step.


FAQs

1. Will Ella push an order straight into my ERP without anyone checking it?

A. Only if every check passes, or every critical check passes with a few warnings. By default, pushed orders land in your ERP's review state (in NetSuite, Pending Approval), so nothing goes live until someone releases it.

2. Can Ella push some lines and hold the rest?

A. By default, no. An order is all or nothing. If one line has a blocking issue, Ella holds the whole order and tells you which line caused it. If your business needs it, this can be configured for your account.

3. I changed an order in my ERP after Ella pushed it. Will Ella overwrite my change?

A. No. Once an order is pushed, Ella never updates it. Make all changes in your ERP.

4. Why don't I see confidence scores in Autonomous Mode?

A. In Autonomous Mode, each check simply passes or fails, so there's no percentage to read. Ella counts the issues instead of averaging them, so many small doubts can't slip through on a good average. The flags and reasons on each line tell you exactly what to check.

5. Ella changed the price on my PO, Why?

A. Ella doesn’t change prices. Ella always pushes the price and quantity on the PO. If they differ from your system, Ella flags the line and explains the difference in the Ella Reason field so you can decide what to do.

6. Why was an order held when nothing looks wrong with it?

A. It was likely held by a rule, such as an order total above your auto-push limit or a rule for a specific customer. The held email says so. Check the order and re-push it from Ella.

7. What should I do when I get a "Pushed with warnings" email?

A. Open the order in your ERP, start with the Areas to Focus field, and check each flagged line against its reason. Make any changes in your ERP, then release the order.

8. Does my customer see the warning or held emails?

A. No. Warning, held, and push-failed emails go to your internal team only. Your customer only receives the acknowledgement on their original thread.

9. What happens if Ella misses an order in my inbox?

A. Every email gets an outcome, and unsure ones wait in the unclassified queue. Your customer also gets a "no order found" reply and can reply on that thread to send it back to Ella. The daily digest lists emails received but not processed, so you can catch anything missed.

10. Does Autonomous Mode work for quotes?

A. Yes. Autonomous Mode covers both purchase orders and quotes.


Still need help? Reach out to our support team at help@wizcommerce.com.