Email log
Email log
The email log is a single list of every email Seller Oracle has ingested, across all your sources. It pulls Gmail, Outlook, and inbound forwarding into one place, so you can see exactly what arrived, how the AI classified it, whether it processed cleanly, and which order or expense it touched.
Most of the time you will not need this page. It earns its keep when something looks off: an order you expected never appeared, an email got classified wrong, or you want to confirm a particular receipt actually came through.
The list
Emails are shown 50 per page, newest first. Each row carries:
- Received: when the email arrived.
- Source: Gmail, Outlook, or Inbound, shown as a coloured badge.
- From: the sender address.
- Subject: the email subject line.
- Type: what the AI classified the email as (order confirmation, dispatch, delivery, expense, and so on). See the email types reference.
- Status: the processing status (processed, failed, needs review, skipped, and the rest). See the email process statuses reference.
- Order: the order this email is linked to, if it created or updated one. Click it to jump straight to that order.
- Tokens: how many AI tokens the email used to process.
- Error: a short error message if processing failed.
Click any row to open the email's detail page.
Filtering and search
The controls above the list narrow it down. They combine, so you can stack a source, a status, and a search term at once.
- Source: filter to one of Gmail, Outlook, or Inbound, or leave it on All Sources to see everything. Gmail and Outlook are kept separate even though both come through connected mailboxes, so if you run both you can isolate one provider at a time.
- Status tabs: the tab bar filters by processing status (All, Pending, Processed, Failed, Skipped, Needs review, Retrying, Deferred). Each tab shows a live count.
- Search: matches on subject, sender address, and order reference. Use it to find a specific receipt or every email tied to one order number.
Use Clear to reset the filters and the search box.
Email detail
Click an email to open it. The detail page shows the metadata Seller Oracle holds on the email and, where it is still available, the original email body.
Header and badges
The top of the page shows the subject, then three badges: the source (Gmail, Outlook, or Inbound), the classified type, and the processing status. These are the same badges you see in the list, repeated here so you can read the email's state at a glance.
Metadata
Below the badges is a table with the sender, the date, the AI token usage (broken down by model), and, where the AI recorded them, a short decision summary and its reasoning. If the email failed, the error message is shown here too.
The email body
Seller Oracle re-fetches the original email body live from the source when you open the page, rather than storing it. HTML emails render in a sandboxed frame; plain-text emails render as text.
Several things can stop the body showing:
- For a Gmail email, if the connection has expired you will see a prompt to reconnect in Settings. Reconnect and the body loads again.
- For an Outlook email, if the Microsoft connection has an auth error (a token refresh failure, for example), the page shows a generic "raw email no longer available" message rather than a reconnect prompt. Go to Settings and reconnect the Outlook account.
- For any email, once the retention period has passed the raw email is removed and the body is no longer available. The metadata above stays, so you can still see what was extracted.
Actions
The actions on an email appear once it has finished processing. A pending email has nothing to act on yet, and the actions are also hidden when the email body is unavailable (retention expiry or an auth error that prevented the fetch).
Mark as Reviewed (Skip)
Marks the email as skipped. Use this for an email flagged as needing review that you have checked and are happy to leave alone. It does not change any order or expense, it just clears the email off your review pile by moving it to the Skipped status.
Reclassify & Reprocess
This is the one to understand before you use it. It tells the AI the email is a different type than it decided, then runs the email through the pipeline again under that new type.
Reprocessing under a new type can move the email's data onto a different order, change the order it already created, or remove that order entirely. If you reclassify an email that has an order attached, a confirmation dialog appears naming that exact order. Read it. If the reclassification would cause Seller Oracle to hide the order it created (for example, because you are marking an order confirmation as irrelevant, personal, customer service, or an expense), the dialog makes clear that the order will be deleted. This cannot be undone from here.
So only reach for Reclassify & Reprocess when the AI genuinely got the type wrong. If the type is right but a figure is off, fix the figure on the order instead. Reclassifying is the heavier tool.
A few details:
- The type dropdown lists every email type except Unknown.
- There is a 5-minute cooldown between reprocessing attempts on the same email, to stop accidental double-runs. If you have just reprocessed it, the page tells you when it will be available again.
Reprocess
A plain Reprocess (re-running the email under the same type, no reclassification) is reserved for Seller Oracle staff. If you think an email needs re-running but the type is correct, use Report a problem on the related order, or reach out to support. The 5-minute cooldown applies here too.
Delete
Removes the email from your email log. This is a soft delete, so it is recoverable on our side, but it disappears from your log and you cannot bring it back yourself from this page. A confirmation dialog appears before it goes. Use it for junk or test emails cluttering the list, not for emails tied to real orders.
When to come here
You will mostly use the email log to answer "what happened to that email?". Common cases:
- An order never appeared. Search the order reference or the retailer's sending address. If the email is there but classified as something other than an order, that explains it (see accuracy and review).
- An email failed. Filter the status tabs to Failed and read the error column. Most failures are transient and clear on the next automatic attempt.
- Something was read wrong. Open the email, check the AI's decision and reasoning, and decide whether the fix is a quick edit on the order or a proper reclassification.
For how emails get classified and extracted in the first place, see how processing works.
Last reviewed: