Marketplace order email parser

Large sellers connect marketplaces to their systems through APIs and integration apps. Many sellers do not, or cannot for every channel: a small marketplace has no API, an integration app costs more than the channel earns, or an account is too new for API access. What every marketplace does provide is an email for each sale. Those emails are written for people, in a different layout per channel, and sellers end up copying orders into a spreadsheet or inventory tool by hand.

ParsedMail reads every channel against one schema, so an Amazon notification, an eBay sale email, an Etsy order and a Shopify notification all become the same JSON object. It complements, and does not replace, official integrations where you already have them. For orders that arrive from business customers instead, see the order email parser.

The value of a marketplace parser is the unified shape. A schema like the one in the example gives you:

• channel as an enum, so reports and routing work per marketplace
• items as a table with SKU, title, quantity and price per row
• prices, shipping and fees as money objects with currency, useful when you sell on Amazon in the US and in Europe
• order_date and ship_by_date as YYYY-MM-DD, so a late shipment check is a simple comparison

Fields a channel does not include stay null. Amazon notifications, for example, often leave out the buyer name and full address, which the seller sees only in Seller Central. The parser never fills such gaps with guesses.

Sale notifications come from many sender addresses. Forward them all to one inbox with Gmail filters or Outlook rules, one rule per marketplace sender. Plus tags can mark the channel in the address, for example [email protected], which helps when one marketplace sends from several addresses. Set allowed senders on the inbox to the marketplace domains, so promotional emails and seller newsletters are logged as blocked_sender and not counted.

Gmail and Outlook send a confirmation email when you add a forwarding address. ParsedMail shows it in the log so you can click the link, and does not parse or count it.

• Inventory. Decrease stock per SKU in tools such as Sellbrite, Cin7, inFlow or a stock sheet, so a sale on one channel is reflected on the others.
• ERP and accounting. Create a sales order in NetSuite, Business Central or Odoo, or a sales receipt in QuickBooks, with the channel as the customer or class.
• Shipping. Send the order to ShipStation or a label tool and flag orders close to their ship-by date.
• Order log. Append every order to a Google Sheet or Excel table, which is often the first step for small sellers. The email to spreadsheet page shows that setup.

Zapier, Make and n8n all receive the JSON with their built-in webhook triggers. Your own code can verify the signature and read the same payload, as described on the inbound email webhook page.

Marketplaces also email cancellations, return requests, refunds and payout summaries. On Growth and Scale, one inbox can hold a sale schema, a cancellation schema and a payout schema, and classification picks one per email. Your automation reads classification.schema and either creates an order, cancels it or posts a payout to accounting. On Starter, use separate inboxes for each kind of email, up to 5 on the plan. Shipping confirmations sent after you buy labels can go to an inbox for the shipping notification parser.

Each sale notification is one email. Notifications rarely have attachments, so they use few or no pages. Starter covers 1,000 emails a month for $49, or $24 a month billed yearly, Growth 5,000 emails for $149 and Scale 25,000 for $499. Resent notifications with the same Message-ID, or the same sender, subject and body within 30 days, are marked as duplicates and not charged. When you reach the limit, parsing pauses and emails are stored until you upgrade or the period renews, and an alert is sent at 80 percent of the email limit.