Custom integration concept · one page

Dairiair, LLC: Amazon Seller Central + rebuilt web store → automatic filter-reminders and one sales view

The problem

GasBGon is a razor-and-blade business: a customer buys a cushion once and then needs a new activated-carbon filter roughly every 3 months (men) to 6 months (women) — the company's own guidance. Yet nothing today knows when any given customer bought a cushion, so nobody reminds them, and the filter sale — the most profitable, most repeatable sale in the business — is left to chance. Orders live in two disconnected places: Amazon Seller Central (the only channel working right now) and the X-Cart storefront on dairiair.com that is currently offline. There is no single place to see what sold, on which channel, at what margin, or which customers are due.

What changes on day one

  • Every cushion order, from Amazon or the web store, starts a filter-life clock — day 75 and day 150 reminders go out automatically by email (and SMS for web customers who opt in). Amazon buyers are reached through the Seller Central buyer-messaging rules that Amazon permits, plus an insert card with a QR re-order link.
  • One morning view of yesterday's and month-to-date sales by channel and SKU, filters-per-cushion, and Amazon ad spend against sales (ACoS / TACoS).
  • A “due now” list — cushion buyers 3–6 months old who have not re-ordered — with the revenue that list represents at one 2-pack each.
  • Low-stock alert on the replacement-filter SKU when weeks-on-hand drops under six, because a filter stock-out breaks the whole cycle.
  • Amazon reviews and Buy Box checked daily; a drop below 4.0 stars or a lost Buy Box pings Jim's phone.

How it fits together

SOURCES INTEGRATION LAYER (AZURE) OUTPUTS Amazon Seller Central SP-API: orders, ads, reviews, Buy Box, FBA inventory Rebuilt web store Shopify / WooCommerce API replaces X-Cart on dairiair.com Payment gateway Authorize.net / PayPal (to confirm) QuickBooks COGS & fees (to confirm) Google Analytics 4 sessions, CVR (to confirm) Legacy mailing list gasbgon.com/signup.htm export Azure Functions nightly + hourly pulls from Amazon SP-API and store API Azure SQL one order table, one customer table, SKU & print master, filter-life cohort calendar Filter-life engine purchase date + product line → due window (3–6 mo; GasMedic longer) → reminder schedule Power Automate triggers reminders, alerts, review requests, stock warnings Microsoft Entra ID sign-in · daily backups Power BI sales view channel · SKU · margin · ads · filter-life clock · inventory Filter reminders Klaviyo / Mailchimp email + SMS day 75 · day 150 · one-click re-order Alerts to Jim's phone low filter stock · rating < 4.0 · Buy Box lost · site down Website sync “in stock” badges & print list on gasbgon.com stay accurate Monthly PDF to QuickBooks channel revenue, Amazon fees, ad spend — ready for the books Dashed boxes = systems not yet verified ("to confirm"). Orange path = the money path: order → filter-life engine → reminder → re-order.

As-is vs to-be

As-is (today)To-be (after go-live)
Where orders liveAmazon Seller Central in one browser tab; X-Cart store offline (523); no combined viewOne order table in Azure SQL fed hourly from both channels; one Power BI page
Filter re-ordersLeft to the customer's memory; no reminder, no subscription, legacy signup.htm onlyDay-75 / day-150 reminders and subscribe-and-save, timed to each customer's own purchase date
Channel marginAmazon fees and ad spend reconciled by hand, if at allGross profit per order by channel and SKU, ads ACoS/TACoS beside it, monthly summary to QuickBooks (to confirm)
Inventory by printSix Signature prints, GasMedic and filters tracked separately on Amazon and the shelfWeeks-on-hand per print across channels; alert under six weeks on the filter SKU
Knowing something brokeHomepage hack and store outage went unnoticed until found externallySite-down, rating-drop and Buy Box-loss alerts to a phone within the hour

Phased approach

Weeks 1–2

Discovery

  • Confirm the systems marked “to confirm”; get Seller Central SP-API and store API access.
  • Agree the filter-life rules per product line and the reminder copy with Sharron.
  • Export the legacy mailing list and historic Amazon order reports (up to 2 years).
Weeks 3–7

Build

  • Azure Functions connectors; Azure SQL model; filter-life engine and cohort calendar.
  • Power Automate flows to Klaviyo/Mailchimp, SMS and phone alerts.
  • Power BI sales view (or the no-licence web version); website stock sync once the rebuilt store is live.
Weeks 8–9

Go-live

  • Back-fill two years of orders so the “due now” list is populated on day one.
  • Reminder flow switched on for web customers first, Amazon-permitted messaging second.
  • Two weeks of hypercare; hand-over with a one-page runbook for Jim.
Also worth knowing: BICS can host a private AI assistant on your own server to draft review responses and customer replies from your FAQ without sending data to a public model; build a small Power App for scanning inbound filter stock and print inventory from a phone; and run all of this on Azure pay-as-you-go, sized for a two-person company, so there is no server to maintain.