An e-commerce founder's inbox is a supply chain in disguise. Suppliers, freight forwarders, marketplace policy teams, 3PLs, agencies, the one wholesale buyer who matters. It all lands in Gmail between order confirmations and app receipts, looking equally urgent.
Waveloom reads that inbox and surfaces the handful of threads that need you. It is not a store app. It does not sit in Shopify, does not touch orders, prices or inventory, and does not answer customer tickets. Those are honest limits.
What your inbound looks like
A supplier saying the next production run slipped two weeks. A marketplace notice about a listing policy change with a deadline. A 3PL flagging a receiving discrepancy. A wholesale buyer asking for updated pricing. A freight quote that expires tomorrow. In Slack, your ops person asking whether to accept a substitute component.
Most of it is noise you should never see. Some of it costs real money if it waits three days.
Sources you would connect
Gmail for supplier, marketplace and partner email. Slack for the ops channel. Notion or Linear if you track launches and purchase orders there. Google Calendar so meeting changes show up in the feed and the brief. HubSpot if you run wholesale outreach.
Web watches for a competitor's product page, a supplier's lead-time page, a marketplace's policy updates, or a question like "tariff changes on my product category." See the market research page for how watches work.
Example cards
Invented examples, alongside the one above.
Order confirmations, app receipts, ad digests, newsletters: dropped. The inbox triage page explains how it decides what to drop.
It executes exactly two background actions, reply by email and reply in Slack, and only after you approve the exact text. It is a reader and a drafter for the business side of your inbox, not an operator of your store.