AgentBIAgent with Business Intelligence for DTC sites

Knowledge base

Sections and entries for this domain, shown from the carrier view of this page.

Operations · Technical

How to keep things running and watched after the changes. Six sections organised by time scale / trigger; entries are recurring actions and on-call duties.

OPS-1 Daily checks (with the batch run)3 item(s)

Availability, 5xx/TTFB trends, crawl errors, price consistency, stock write-back

Carrier on this page:Knowledge base — what counts as an anomaly vs noise.

Open-source tools:Uptime KumaurlwatchabiFlow

Skills:Daily-check review checklist

  • Review the daily batch results

    OPS-1-1

    Day-over-day 5xx and TTFB shifts, crawl-error spikes and feed/landing-page price mismatches usually appear before traffic drops.

    • Follow trends from one vantage only; never compare absolute values across vantages (KR vs CN)
    • Classify feed-window drop-outs separately — never count them as delistings or price changes; the event carries no information

    View detail

  • Same-day availability review of key pages with an exception log

    OPS-1-2

    The batch gives trends; on-call work is whether these key pages are still reachable today. An exception without context cannot be judged as a blip or a sustained problem tomorrow.

    • Spot-check availability and HTTP status of the homepage, category, key product and checkout pages daily, compared with yesterday from the same vantage
    • Log site, vantage, time and previous baseline for each exception, classify one-off blips separately, and never change definitions or re-run to force a green result because of a single day numbers

    View detail

  • A daily checklist and on-call handover log

    OPS-1-3

    Ad-hoc reviews miss items and lose all context on handover. Fix the pages to check, the comparisons to make and the fields to log in one checklist.

    • Keep a fixed checklist of key pages, same-vantage comparisons, price/stock consistency and crawl errors, ticked item by item
    • Log open exceptions and the previous baseline at handover; do not skip the record just because nothing fired

    View detail

18 more items not shownSign up free

OPS-2 Periodic review (weekly / monthly)3 item(s)

Coverage and index growth, CWV percentiles, launch cadence, competitor-wide repricing

Carrier on this page:Knowledge base — metric definitions and baselines.

Open-source tools:MetabaseApache Superset

Skills:Periodic review template (weekly / monthly)

  • Monthly field-coverage and CWV percentile report

    OPS-2-1

    Single readings are noisy; monthly percentiles and coverage deltas are what carry signal.

    • Measure field coverage per category and prioritise low-coverage categories for the next backfill
    • Use CrUX monthly percentiles for CWV rather than one Lighthouse score; allow at least a week after a change before judging it

    View detail

  • Weekly / monthly review of index growth and launch cadence

    OPS-2-2

    Many new listings with no index growth points to a template or feed problem; looking at index totals without launch cadence mistakes no new listings for lost indexation.

    • Track daily new listings alongside newly indexed ones; separate few listings added from added but not indexed
    • Correlate index changes with release windows and template edits to see whether we caused them; never conclude from a single crawl

    View detail

  • Periodic watch on competitor-wide repricing

    OPS-2-3

    A single discounted item is noise; a store- or category-wide repricing can shift our own baseline. Reviews must tell the two apart.

    • Measure how broad a competitor price change is per category; only widespread moves enter the pricing-baseline discussion
    • Log the observation window alongside the magnitude so a one-off promo is not mistaken for a trend

    View detail

18 more items not shownSign up free

OPS-3 Change management (event-driven)3 item(s)

Pre/post-release re-scans, release windows, rollback artefacts

Carrier on this page:Knowledge base — release process and rollback SOP.

Open-source tools:changedetection.ioHuginnabiFlow

Skills:Release window and rollback artefact check

  • Re-scan and regression-test around releases

    OPS-3-1

    Template, routing and bulk price changes are the most likely to reintroduce issues already fixed.

    • Keep a baseline of key pages before release, then re-scan homepage, category and key product pages afterwards
    • Retain rollback artefacts; after bulk price changes force a feed refresh and compare all three amounts

    View detail

  • Release windows and rollback artefact management

    OPS-3-2

    Whether a bad change can be rolled back in one step depends on keeping a fully restorable artefact before release and a defined window. Ad-hoc edits without a rollback artefact make recovery time unpredictable.

    • Package templates / routes / dictionaries / data files into one swappable artefact; keep a dated, verified-restorable rollback copy before each release
    • Fix release windows and avoid one-off production edits outside them; log which files changed each time and roll back by swapping the whole artefact, not by patching files individually

    View detail

  • Regression scope for payment / logistics / platform changes

    OPS-3-3

    When an upstream changes fees, tracking-number formats or feed specs, we are affected passively. Define which pages to regression-test before release instead of re-testing everything.

    • Name the affected tools, checklist items and pages in the change ticket and scope regression from that dependency map
    • Re-test only the affected surface and log the result; do not re-run the full suite for a single upstream change

    View detail

18 more items not shownSign up free

OPS-4 Alerting and response (threshold-triggered)3 item(s)

Which metrics deserve alerts, severity, false-positive control, response SOP

Carrier on this page:Knowledge base — severity levels and threshold rationale.

Open-source tools:PrometheusGrafanaHealthchecksSentryabiFlow

Skills:Alert response SOP and escalation

  • Alert severity and false-positive control

    OPS-4-1

    Under the noise-floor definition, alert only on signals that should fire — otherwise alerts are quickly ignored.

    • Limit alerts to availability, price inconsistency and stock conflicts; assign severity and response deadlines
    • Attach context (site, vantage, window, previous baseline) rather than a bare number

    View detail

  • Alert response SOP and escalation path

    OPS-4-2

    An alert nobody owns, or one that is never closed, is no alert at all. Beyond severity, spell out who does what within what time, and when it escalates.

    • For each severity, define the owner, response deadline, response steps and close condition, and archive the closure record
    • Escalate automatically on timeout; forbid re-run until green or lowering the threshold as a response — adjust only under the noise-floor definition

    View detail

  • Periodic recalibration of thresholds and the noise floor

    OPS-4-3

    As scale and traffic change, once-good thresholds drift. Adjust them only under the stated definition, never just to silence an alert.

    • Revisit thresholds and the noise floor monthly against historical distributions; log the rationale and effective date in the changelog
    • Keep calibration separate from response: calibration changes definitions, response fixes the site; never lower a threshold instead of fixing the cause

    View detail

18 more items not shownSign up free

OPS-5 Data and definition upkeep (continuous)3 item(s)

Daily series and snapshots, vantage labels, definition changes, citation readiness

Carrier on this page:Knowledge base — changelog and data dictionary.

Open-source tools:BeszelabiFlow

Skills:Snapshot retention and definition changelog

  • Vantage labels, daily series and a definition changelog

    OPS-5-1

    Once a definition changes, the historical series is no longer directly comparable; before citing anything publicly, confirm the route is actually live.

    • Label every number with vantage and date, keep the daily series unbroken and fields frozen; log definition changes in the changelog
    • Before stating where our data can be checked, confirm that route is actually anonymously readable in production

    View detail

  • Snapshot retention and citation-readiness checks

    OPS-5-2

    A broken historical series cannot be rebuilt, so keep daily snapshots with frozen fields. Before claiming where our data can be checked, confirm that route is truly anonymously readable in production.

    • Archive daily snapshots by date, freeze fields, keep the series unbroken; definition changes apply forward only and are logged in a changelog, never back-applied
    • Before listing a verifiable route in public material, hit the production build once with an anonymous request and confirm it returns data, not a login page or a stale build

    View detail

  • Notifying definition changes and preserving comparability

    OPS-5-3

    A definition change breaks direct comparison with history, and public material still on the old definition leads readers to wrong conclusions.

    • Record the effective date, affected fields and whether a change is back-comparable; leave historical data untouched
    • Label public material with the current definition version and state explicitly when two versions are not directly comparable

    View detail

18 more items not shownSign up free

OPS-6 External cadence tracking (externally driven)3 item(s)

GMC / Meta policies, search algorithm updates, UCP and protocol progress, platform rules

Carrier on this page:Knowledge base — external policy timeline.

Open-source tools:urlwatchchangedetection.io

Skills:External policy timeline log

  • Track platform policies and protocol progress

    OPS-6-1

    GMC / Meta product specs, UCP and .well-known progress, and search algorithm updates change which practices still hold.

    • Record only changes relevant to our definitions, noting which checklist items or tools they affect
    • Assess new agent UAs / protocol fields before adding them to the scan scope; never extend scan_batch.py fields directly

    View detail

  • An external policy timeline with impact mapping

    OPS-6-2

    Seen piecemeal, policy changes are easy to miss and hard to map to our own practices. A dated timeline that marks which checklist items each change affects beats a folder of bookmarked links.

    • Log only GMC / Meta / search / UCP changes relevant to our definitions, each with date, source and the checklist items or tools affected
    • Route new agent UAs or protocol fields through impact assessment before any change; do not extend scan script fields directly, and keep the timeline as part of the changelog

    View detail

  • Compatibility check for protocol field changes

    OPS-6-3

    When UCP / .well-known adds or renames a field, existing tools and checklist items may read the old shape. Check compatibility before pulling it into the definitions.

    • Map old vs new fields to the affected scan readings and checklist items, marking added, renamed or deprecated
    • Confirm the old field is still readable and the new one has a fallback before adopting it; never extend scan script fields directly

    View detail

18 more items not shownSign up free

Operations · Business

The business the store owner actually runs. Six sections in lifecycle order: setup → listing → sales → after-sales → supply chain → review. KB articles and Skills carry most of this side; Tools are downloaded and run in the user's own environment against their own data in our format (see v3 §2.3).

BIZ-1 Store setup3 item(s)

Entity, platform, payments, tax, logistics, brand

Carrier on this page:Knowledge base — setup checklist and policy templates

Open-source tools:Matomo

Skills:Store-setup self-check

  • Settle the entity and payment rail first

    BIZ-1-1

    Entity, tax and payment rail determine whether you can take money and run ads at all — settle them before listing products.

    • Fix the legal entity, tax setup and payment rail (Stripe / third party / Creem TBD), together with 3DS and chargeback policy
    • Spell out shipping cost, duties, delivery time and returns address; keep policy pages and checkout consistent

    View detail

  • Brand, domain and multi-market baseline setup

    BIZ-1-2

    After entity and payment rails are settled, fix domain structure, default locale/currency and brand facts before listing — changing them later ripples through URLs, feeds and already-indexed pages.

    • Decide single-domain multilingual vs per-market domains, set default locale / currency / timezone, and freeze the URL scheme rather than changing it later
    • Write brand, contact and credential facts as a citable block in the about page and structured data, consistent across markets

    View detail

  • Pre-launch credentials and brand filing checklist

    BIZ-1-3

    After entity and rails are settled, missing licences, trademarks or platform filings block listing and ads, and the requirements differ by market.

    • List licences, trademark/brand authorisation and platform filings per market, with the documents ready for each
    • Keep credential ids and expiry dates in the setup file and align entity facts across policy pages and structured data

    View detail

18 more items not shownSign up free

BIZ-2 Sourcing and listing3 item(s)

Sourcing, costing, pricing, listing, localisation, feed sync

Carrier on this page:Knowledge base — margin structure and listing standards

Open-source tools:PriceBuddy

Skills:Test-batch sourcing and pre-listing check

  • Margin structure and a pre-listing checklist

    BIZ-2-1

    Marking up only the goods cost omits inbound freight, duties, platform fees and return losses; missing listing fields poison every downstream step.

    • Compute landed margin per market (inbound freight, duties, platform fees, return losses) before setting price and promo floors
    • Walk the pre-listing checklist: attributes, image alt text, locale/currency, SKU, feed sync, stock initialisation

    View detail

  • Validate sourcing with a small test batch

    BIZ-2-2

    Going straight to a large buy turns a sourcing mistake into dead stock. Run a small batch first to surface real demand, return reasons and fulfilment cost before scaling.

    • Test each new product in a small batch, log sell-through, return reasons and landed cost, and decide on replenishment from measured data rather than projected margin
    • Feed test results back into size charts and product copy before committing to a large buy and the listing checklist

    View detail

  • Category attributes and image asset standards for listing

    BIZ-2-3

    Half-filled category attributes, missing alt text or inconsistent image sizes cost feed quality and comparison agents, and cost far more to fix later than at listing time.

    • Define required attributes per category (material, size, audience …) and validate completeness at listing time
    • Standardise main-image size and ratio, write real alt text, and map variant images one-to-one to SKUs

    View detail

19 more items not shownSign up free

BIZ-3 Traffic and acquisition3 item(s)

SEO, paid ads, social/influencers, affiliates, content, repeat visits

Carrier on this page:Knowledge base — channel structure and metric definitions

Open-source tools:MatomoPlausible AnalyticsPostHog

Skills:Channel mix and CAC baseline

  • Channel mix and a CAC baseline

    BIZ-3-1

    Without per-channel baselines, a total traffic number cannot tell you which channel to scale or stop.

    • Track spend and conversions separately for SEO, paid, social, influencers and affiliates; establish CAC baselines before optimising
    • Write category and help pages as citable facts so shopping assistants have something to quote

    View detail

  • Repeat-visit and retargeting baselines

    BIZ-3-2

    Focusing only on acquisition ignores existing customers. Build separate baselines for repeat visits, retargeting conversion and member retention to decide whether budget belongs in acquisition or retention.

    • Track repeat purchase, retargeting conversion and opt-out rates separately from new customers; establish baselines before increasing spend
    • Keep email / retargeting claims consistent with landing pages, and sync promo and member prices across detail page, checkout and feed

    View detail

  • Attribution and settlement checks for influencers and affiliates

    BIZ-3-3

    If influencer and affiliate conversions blur into organic traffic, neither commission nor ROI is trustworthy, and renewal decisions become guesswork.

    • Give each influencer/affiliate a distinct link or code and reconcile conversions and commission per contract period, not from totals
    • Remove returns and opt-outs before computing ROI and fix the settlement definition in the contract and changelog

    View detail

18 more items not shownSign up free

BIZ-4 Sales and conversion3 item(s)

Promotions, cart and checkout, AOV, cart recovery, peak-season cadence

Carrier on this page:Knowledge base — checkout-friction playbook

Open-source tools:PostHog

Skills:Cart-abandonment triage and AOV review

  • Locate cart abandonment and keep promo prices consistent

    BIZ-4-1

    Which step loses the cart (shipping, signup, payment) determines the fix; site-wide discounts usually mask the real friction.

    • Break abandonment down by checkout step, fix only that step, and do not mask it with a site-wide discount
    • Before a promo, reconcile amounts across detail page, cart, checkout and feed; never leave the old price on the landing page

    View detail

  • Raise AOV and attach rate structurally

    BIZ-4-2

    Raising AOV by price hurts conversion. Bundles, add-ons and free-shipping thresholds should follow real attach patterns, not arbitrary product pairings.

    • Derive bundles and add-ons from real order co-occurrence, expose them as structured recommendations rather than forced pairings, and watch their effect on conversion and returns
    • Set free-shipping thresholds from the AOV distribution and reconcile all four amounts before a promo so the threshold does not reintroduce checkout friction

    View detail

  • Peak-season cadence and rollback plan

    BIZ-4-3

    A peak season stacks price, template and stock changes, which is exactly when fixed issues reappear. Cadence and rollback need to be set in advance.

    • Split warm-up / launch / encore into explicit windows, each with a key-page baseline and rollback artefact beforehand
    • After the promo, walk a checklist to remove prices and copy, then confirm the feed refresh and all four amounts back to normal

    View detail

18 more items not shownSign up free

BIZ-5 Fulfilment and after-sales3 item(s)

Shipping, tracking, duties, returns, support, reviews and chargebacks

Carrier on this page:Knowledge base — fulfilment and returns SOP

Skills:Fulfilment, after-sales and ticket SLAs

  • Shipment tracking and feeding return reasons back

    BIZ-5-1

    Without order-status write-back or return-reason classification, the same problems keep recurring in sourcing and size charts.

    • Write order status and tracking numbers back in real time; state duties and customs responsibility on product pages
    • Classify reviews and returns by cause (sizing / quality / logistics) and feed results back into size charts and sourcing

    View detail

  • Support SLAs for tickets, chargebacks and negative reviews

    BIZ-5-2

    Slow after-sales handling turns into chargebacks and bad reviews. Setting response and closure deadlines per ticket type is far cheaper than damage control later.

    • Classify tickets as logistics / sizing / quality / refund, set first-response and closure deadlines per type, and escalate on timeout
    • Route chargebacks and negative reviews through a separate root-cause pass and feed results back into size charts, copy and sourcing so the same cause does not recur

    View detail

  • Keep support FAQ in sync with review root causes

    BIZ-5-3

    When reviews clearly point to sizing but the FAQ still says the old thing, the same tickets keep recurring.

    • Feed return/review root causes back into size charts, product copy and the support FAQ each quarter
    • Tag each FAQ entry with its evidence and update date, and keep policy pages, checkout and support scripts consistent

    View detail

18 more items not shownSign up free

BIZ-6 Supply chain and business review3 item(s)

Replenishment, inventory turns, stockouts and slow movers, margin, CAC/LTV, cash flow

Carrier on this page:Knowledge base — metric definitions and review templates

Open-source tools:MetabaseabiFlow

Skills:Monthly business decision review

  • Replenishment, stockouts/slow movers and metric definitions

    BIZ-6-1

    Stockouts and slow movers need different treatments; if metric definitions change monthly, reviews lose comparability.

    • Replenish from turnover and demand forecasts, treat stockouts and slow movers separately, and review supplier terms alongside cash flow
    • Split GMV, margin, CAC, LTV, return rate and cash flow by channel; freeze definitions in a changelog instead of redefining them monthly

    View detail

  • Monthly decision review of CAC / LTV and channel profitability

    BIZ-6-2

    Once definitions are frozen, the point is to use them: which channel to scale or stop, which category only looks busy — each should turn into a concrete action for next month.

    • Compute CAC, LTV, margin and return rate per channel / category under one frozen definition, and state explicit scale / cut / stop decisions
    • Turn each decision into a tracked next-month action; definition changes apply forward only and are logged in a changelog, never redefined monthly so reviews stay comparable

    View detail

  • Quarterly review of inventory turns and slow movers

    BIZ-6-3

    Stockouts need replenishment and slow movers need clearing — opposite actions. Watching total inventory alone hides both.

    • Compute days-of-turn per SKU, keep stockouts and slow movers on separate lists with their own actions (replenish / clear / delist)
    • Review supplier terms, warehouse capacity and cash flow together and turn conclusions into next-quarter purchasing

    View detail

18 more items not shownSign up free