Every platform,
one operating floor.

What it does

The desk sales and CS reps use instead of clicking through NetSuite: which colours of a product exist, how many are in stock and when more lands, what margin a deal makes, and how much discount room is left. Reps never see cost — they enter a price and get a verdict: Approved (margin ≥ 28%), Manager approval (15–28%), or Not permitted. Gated deals file a request into the approver's queue; nothing is ever pushed to NetSuite.

Who uses it

Sales and customer-service reps (the largest membership of any app); Alexia decides requests.

Where to start

• Sign in with FlooringID — the same login as everything else.
• Catalog tab → search a product → a swatch grid with live stock and restock dates.
• Add colours to the cart → Margins tab → type a price, ZIP and state → live freight and the band verdict.

What it does

Today's and this week's sales, margin and sample orders pulled live from NetSuite — by channel, by day, by order, with the sales agent on each one. Top categories and product groups over the trailing twelve months, with drill-in charts.

Who uses it

Leadership and sales management — the "how are we doing today" screen.

Where to start

• Sign in with FlooringID.
• This week for today against the week (Sun–Sat); Orders → click an order for ship-to, lines and agent.
• Products → search any product and group by product, variant or SKU.

What it does

Replaces the monthly Excel packs: sales and orders per agent, quotes, CSAT, how fast support answers calls and chats, refunds and cancellations, web traffic, and staffing against expected volume. Every number is held to within 2% of the old reports. Zendesk and NetSuite refresh every four hours; the slow Magento scan runs on demand.

Who uses it

IS and CS managers, leadership.

Where to start

• Sign in with FlooringID.
• First visit: the built-in guide walks through every page.
• Managers: edit monthly goals inline on each scorecard.

What it does

Every Zendesk Talk call is recorded, transcribed per speaker, and read by a local AI that calls it a win, loss or neutral, summarises it, tracks the customer's mood, and fills out the same QA scorecard (support) or 26-point checklist (sales) the teams already use by hand. Managers can correct a label; corrections feed a rubric the AI proposes and a human approves. No audio ever leaves the building.

Who uses it

Sales and CS managers, training, leadership.

Where to start

• Sign in with FlooringID; new calls show a badge in the top bar.
• Open any call for the transcript, score and mood track; compare agents on the leaderboard.
• The Patterns view shows what winning calls do differently; search past calls by meaning.

What it does

Every customer review and feedback signal in one place — BazaarVoice, Zendesk CSAT and Shopper Approved today; Google, Reddit and BBB planned. Each item gets a sentiment, negative reviews get an AI-classified root cause, and where an agent handled the order or ticket the item is attributed to them for per-agent scorecards. Product reviews with no agent count toward brand health, not scorecards — on purpose.

Who uses it

CS and IS managers; Dustin keeps the feeds flowing.

Where to start

• Sign in with FlooringID.
• Agents view → volume, average rating and % negative per agent.
• Feeds ingest daily on their own; there is nothing to run by hand.

What it does

FlooringInc's own product binder — names, brands, specs, descriptions, photos, categories and the web text the site shows — built to replace Akeneo before that contract ends around September 2026. It mirrors Akeneo nightly and keeps every hand-edit as a protected "owned change" that a re-copy never wipes. The new storefront already reads its catalog from here; a product-level edit reaches staging in about a minute.

Who uses it

Catalog managers (Leah first), platform admins; the storefront reads it as a service.

Where to start

• Sign in with FlooringID; only FloorPIM members get in.
• Catalog → stack filters (family, status, for-sale, edited…) and save the view for others.
• Open a product → grouped editor, live completeness score, and the live Magento value beside yours.

What it does

One read-only reference site for every product we sell, modelled on Lenovo's PSREF: the full spec table, every colour and size variant, datasheets and install, care and warranty PDFs on one page. About 2,000 pages are pre-built and rebuilt nightly from Akeneo, so it stays fast and current. A Tools page carries quoting calculators; an MCP Access page lets AI assistants query the same catalog.

Who uses it

Sales, CS, ops — anyone who needs specs in front of a customer.

Where to start

• Sign in with FlooringID.
• Press / to search by name, SKU, material or family.
• Bookmark product pages — they survive the nightly rebuild.

What it does

The screen the content team uses to manage the photos next to products on flooringinc.com. Find a product, see all of its image slots, then drag, drop, replace, reorder or delete. Behind the scenes it uploads to Canto, writes the link into Akeneo, and shows a status banner while the Adobe connector (roughly every 16 minutes) carries the change to the live site. It keeps no database of its own.

Who uses it

Content and web team.

Where to start

• Sign in with FlooringID.
• Search a product → its image slots.
• Drag a file in; the Canto upload and the Akeneo update happen in one step.

What it does

The owned, ground-up replacement for Adobe Commerce (Magento): a Next.js storefront on a Medusa commerce engine, with the catalog fed by FloorPIM. Built to win on SEO, speed and UX, and to be AI-native. Feature-complete on mocks and deployed to staging; waiting on the real payment, tax and shipping integrations and the money-path review.

Who uses it

Kurt owns the product; Mert runs the deploy and the FloorPIM bridge; the whole team can browse. Merchandisers later, through the staff console.

Where to start

• No login — open it and browse. It is hidden from Google, not from you.
• Nothing here serves a paying customer; production is still Akeneo → Magento.
• Code pushes reach staging within about three minutes; FloorPIM edits within about four.

What it does

Answers the buying team's question — what do I reorder, and how urgently? It pulls live inventory, sales, POs, shipments and refunds from NetSuite, works out velocity and seasonality per SKU, and colour-codes BACKORDER / RED / YELLOW / GREEN with days of stock left (and a "Days +PO" column that counts incoming orders). It also pushes honest "ships by" dates to the catalog and storefront, emails backordered customers through Klaviyo, grades vendors, and carries a local chat assistant.

Who uses it

Purchasing, inside sales, leadership.

Where to start

• Sign in with FlooringID.
• The dashboard sorts the most urgent SKUs to the top.
• Use "Discontinued only" to manage sell-through; export CSV or Excel from the toolbar.

What it does

The console for how each product ships and what the customer is charged: the recipe (free, $ per lb, or a live carrier quote), the upcharge, and the fulfilment warehouses. Read and explain any rule, ask the AI why a product ships for $X to New York, and — if you are on the editor allowlist — apply a proposed change through the same validated write path the old CMS used. The origin-coverage map flags fake addresses and single-origin risk.

Who uses it

Merchandising — Kurt and Chuck edit; Alexia drives the regional upcharges.

Where to start

• Sign in with your CMS (Cognito) account — this one is not on FlooringID.
• Pick a product → its variants, swatches and the rule each resolves to.
• AI proposals show a diff card; nothing is written until a human clicks Apply.

What it does

Every night it behaves like a real shopper and runs an actual checkout on our store and on four rubber-flooring competitors (AFM, RFD, Great Mats, RF4U) in four US regions — unit price, real shipping including LTL, sales tax, promo and grand total. Twice a week a colour-coded Excel lands in your inbox. The dashboard adds AI match scoring, autoresearch, a catalog crawler and the Revenue Leaks report (GA4 traffic × cost × scraped prices).

Who uses it

Pricing, marketing, leadership.

Where to start

• Sign in with FlooringID.
• Pick a SKU → its price history beside the matched competitor SKU.
• Scrape runs at 2:00 AM; the email goes out Wednesday and Sunday at 8:30.

What it does

"What did this order actually make us?" Revenue, true cost of goods, kit rollups (which NetSuite does not do) and actual freight in one place — per order, product, channel, brand and family. Evidence-first: every cost says how it is known (a paid vendor bill, a NetSuite estimate, a catalog average), and a missing cost shows as unknown, never $0.

Who uses it

Kurt and Leah own it; Liz audits orders; finance and leadership read it.

Where to start

• Sign in with FlooringID. The old margin.flooringinc-api.com address still works.
• Cockpit → whole-book margin and where the profit lives, month over month.
• Orders → sort ascending by margin, tick what you have audited, open a case; export CSV.

What it does

Watches the accounts-payable inbox and reads vendor invoices and carrier freight bills with local AI — nothing financial goes to a cloud model. Product invoices are matched to their NetSuite PO with a three-way check; a reviewer approves a pre-filled screen and the Vendor Bill lands in NetSuite with the PDF filed to Drive. Freight bills get predicted accounting codes and post as expense bills or a finance-template spreadsheet. Bundled PDFs split per invoice; bulk approve runs in batches.

Who uses it

Accounts payable and accounting.

Where to start

• Sign in with FlooringID. The old ap.flooringinc-api.com address still works.
• The queue lists every invoice waiting for review.
• Open a row → the PDF, the matched PO and the extracted lines side by side; approve, or bulk-approve a filtered batch.

What it does

The read model of the whole estate: a nightly lake over FlowCast, MarginPlatform, CompShop, AP, NetSuite, Akeneo and GA4, plus a company memory that answers "where did we decide X" from sessions, the wiki, mail, meetings and Jira. On top of it sit the Ticket Desk, where anyone files a Jira-style ticket per app and a Claude session picks it up, and the BI Hub, a ranked feed of things to act on with honest date windows and comparisons.

Who uses it

Everyone files tickets; Mert runs it; the agents do the work. A 07:00 daily brief lands in Mert's inbox.

Where to start

• Sign in with FlooringID.
• /tickets → New ticket → pick the app, describe it plainly, attach screenshots; the agent asks you if it needs a decision.
• /bi → KPI header and ranked insights; wow / mom / yoy presets, or type a date range.

What it does

The one login for the suite. It mints every session, re-verifies email 2FA every 90 days, and answers each app's "is this person a member, and with what role?" live on every request. Platform admins invite people per app; a 24-hour activation link does the rest.

Who uses it

Everyone, every day; platform admins manage membership.

Where to start

• /login — the same email and password everywhere.
• /account → your sessions and activity; sign out everywhere from there.
• Locked out? Five failed logins pause you for 30 minutes; use "forgot password".