Skip to main content
Email remains the most common way B2B customers send purchase orders, but managing POs inside a shared inbox is slow and error-prone — orders get buried, attachments need manual re-entry, and there’s no easy way to track what’s been confirmed. StackCube gives you a dedicated order email address that your customers send to directly. When a PO arrives, StackCube reads the message body and any attachments, extracts the order lines, and creates reviewable candidates your team can approve from the order list — no inbox digging required.

​
How email orders work

1

Share your StackCube order email address

Every StackCube workspace has a dedicated order email address (for example, orders@yourcompany.stackcube.io). Share this address with your customers as the destination for all purchase orders. You can include it in your email signature, invoices, or customer onboarding materials.
2

Customers send their purchase order

Customers email their PO to your order address. They can write the order directly in the email body, attach a PDF purchase order, or attach an Excel order form — StackCube handles all three formats in the same message. No special formatting is required on the customer’s side.
3

StackCube reads the message and organizes candidates

As soon as the email arrives, StackCube parses the body text and any attached files. The AI identifies item names, quantities, SKUs, and any notes, then organizes them into structured order candidates. If something is ambiguous — a product name that matches multiple SKUs, for example — StackCube flags it for your review rather than guessing.
4

Your team reviews and approves in the order list

Open the StackCube order list to see every incoming order from every channel, including email. Review the extracted candidates, make any corrections, and approve. The original email and attachments are linked to the order so you can always refer back to the source.

​
Supported email formats

StackCube can extract order information from the following sources within a single email:
  • Body text — line items written directly in the message, in any common format (lists, tables, or plain prose)
  • PDF attachments — scanned or digital purchase orders, supplier forms, and printed order sheets
  • Excel attachments — .xlsx and .xls order forms, including multi-sheet workbooks
If a customer sends both a body-text summary and a PDF attachment in the same email, StackCube reads both and merges the candidates. You’ll see everything in one review, not two separate orders.

​
Workflow options

StackCube supports three common ways customers interact with your order email address, so you don’t need to ask anyone to change their habits.

Direct email

The simplest setup. The customer addresses their PO directly to your StackCube order address. This is the recommended workflow for new customers you’re onboarding.

CC workflow

The customer CC’s your StackCube order address while keeping their own team or your account manager on the main To line. StackCube picks up the order from the CC, and everyone stays informed.

Forwarded PO threads

A customer or your own team member forwards an existing email thread — including any previous replies and attachments — to the StackCube order address. StackCube reads the full thread and extracts the most recent order details.
Ask customers who already send POs to your regular inbox to simply CC the StackCube order address going forward. This lets their existing workflow stay intact while giving your team the benefits of the review queue immediately — no cutover required.

​
Frequently asked questions

If the AI cannot match an item with sufficient confidence — for example, the product name is ambiguous or the quantity is missing — it creates a candidate flagged for review rather than skipping the line. Your team sees the original text alongside the candidate and can fill in or correct any details before approving.
Yes. All emails to your order address land in the same StackCube review queue, regardless of sender. Each order is attributed to the sender’s email address, so you can filter and sort by customer in the order list.
Yes. StackCube keeps a reference to the original email — including body text and attachments — linked to each order. You can open the source email directly from the order detail view for audit or dispute purposes.
StackCube creates a new order candidate for each email received. If a customer sends a corrected PO, you’ll see both in the queue. Review the updated one and mark the original as superseded, or add an internal note to the order for your records.