Question 1

What does done-for-you multi-POS receipt integration actually deliver?

Accepted Answer

Completions builds and operates a receipt-integration bundle on the walk-in-phone-attribution agent for multi-location retailers, multi-unit restaurant operators, and franchise systems running 50-1,500 locations. Receipt ingestion: connects to 25+ POS and ordering vendors (Square, Toast, Clover, Shopify POS, Lightspeed, Revel, Aloha, Micros, Oracle Symphony, NCR Counterpoint, TouchBistro, Talech, Vend, Erply, Heartland Retail, Cake, ParTech, Brink, Salido, Upserve, Bbot, Olo, DoorDash, Uber Eats, Grubhub, and the Restaurant365 + Compeat + Crunchtime + MarginEdge + Plate IQ + xtraCHEF + BevSpot + BinWise + DAVO back-office stack) via API, webhook, SFTP, and file-drop ingestion paths through the operator ELT layer (Fivetran, Airbyte, Stitch, Singer-tap implementations, Hightouch, Census). Tender-and-line-item normalization: maps every receipt into a canonical schema covering header, tender, line-item, discount, tax, tip, loyalty, payment-method, modifier, employee, station, shift, promotion, and comp fields, with per-vendor mapping libraries that detect schema drift, field renames, and field deprecations as POS vendors ship API updates. Visit-joining: joins receipts to in-store visits through probabilistic matching across timestamp windows, location device IDs, WiFi probe captures, BLE beacon proximity, payment tokens, loyalty IDs, mobile numbers, emails, and where deployed, image signals, with confidence-tier annotation and a human-in-the-loop review queue for low-confidence matches. Marketing-attribution: attributes joined receipts back to marketing touches across paid search, paid social, paid display, paid video, organic search, organic social, email, SMS, push, direct mail, OOH, radio, TV, referral, partnership, event, influencer, and PR touch types, emitting last-click, first-click, linear, time-decay, position-based, data-driven, Shapley-value, Bayesian, Markov-chain, and incrementality (causal-uplift) views for the operator marketing mix model and CFO ROAS reporting. The compliance overlay covers HIPAA (pharmacy POS), DEA Schedule II-V (controlled-substance POS), Metrc 12-state (cannabis POS), DISCUS (alcohol POS), FDA tobacco (tobacco POS), state licensing boards (service-vertical POS), PCI DSS, GDPR, CCPA, and state receipt-retention rules where applicable. Operator owns the receipt data inside operator data infrastructure (Snowflake, BigQuery, Databricks, Redshift, or Postgres), the normalization mapping code in the operator repo with operator-controlled deploy pipeline, the visit-joining model code aligned with the operator data-science team, the marketing-attribution model code aligned with the operator marketing and finance teams, per-vendor API and webhook and SFTP credentials under operator billing, the attorney-approved compliance overlay rule library, LLM prompts in the operator repo, and the audit trail in operator-controlled storage with WORM retention where HIPAA, DEA, Metrc, or PCI DSS rules require it. Completions owns the orchestration knowledge.

Question 2

Why is multi-POS receipt integration typically operator-side rather than POS-vendor- or ELT-vendor-shipped?

Accepted Answer

Six engineering surfaces sit between operator data infrastructure and a working receipt-integration bundle, and they sit outside the design center of the POS, ordering, back-office, and ELT ecosystems that own the upstream primitives. Surface 1 — Multi-vendor receipt ingestion: Square, Toast, Clover, Shopify POS, Lightspeed, Revel, Aloha, Micros, Oracle Symphony, NCR Counterpoint, TouchBistro, Talech, Vend, Erply, Heartland Retail, Cake, ParTech, Brink, Salido, Upserve, Bbot, Olo, DoorDash, Uber Eats, and Grubhub each ship strong receipt APIs, but the connector-maintenance burden across 25+ vendors with deprecations and schema changes every 3-6 months is operator-side. Fivetran, Airbyte, Stitch, Singer-tap implementations, Hightouch, and Census ship strong ELT primitives but stop short of canonical receipt normalization. Surface 2 — Tender-and-line-item normalization: the canonical schema across header, tender, line-item, discount, tax, tip, loyalty, payment-method, modifier, employee, station, shift, promotion, and comp dimensions, with per-vendor mapping libraries, is operator-side modeling. Surface 3 — Visit-joining: probabilistic matching across timestamp, device-ID, WiFi probe, BLE beacon, payment token, loyalty ID, mobile number, email, and image signals with confidence-tier annotation is operator data-science capacity. Surface 4 — Marketing-attribution: attribution across 18 touch types and 10 attribution models, including incrementality with causal-uplift methodology, is operator-side modeling that has to be reconciled with the operator marketing mix model and CFO ROAS reporting. Surface 5 — Per-vendor connector maintenance: POS vendors ship API updates every 3-6 months, so the connector layer needs ongoing vendor-coordination capacity. Surface 6 — Compliance overlay covering HIPAA, DEA Schedule II-V, Metrc 12-state, DISCUS, FDA tobacco, state licensing boards, PCI DSS, GDPR, CCPA, and state receipt-retention rules is operator-counsel-side. Completions runs orchestration across all six surfaces under one Tier 3 Fractional CMO with AI Swarm engagement; operator owns the artifacts and can in-house at any time.

Question 3

What does the engagement look like across Tier 1, Tier 2, and Tier 3?

Accepted Answer

Tier 1 AI Readiness Assessment ($10k, 2-3 weeks, diagnostic): audits the six surfaces above against the operator stack — what POS, ordering, and back-office vendors are in place, what ELT layer is wired today, what canonical normalization exists, where visit-joining and attribution gaps live, and where the per-vertical compliance overlay needs counsel review. Tier 2 AI Swarm Setup Sprint ($25-50k, 4-8 weeks): builds the receipt-integration bundle on the walk-in-phone-attribution agent, with the marketing-attribution model reviewed by operator marketing and finance teams and the compliance overlay rule library reviewed by operator counsel. Tier 3 Fractional CMO with AI Swarm ($15-25k/month, 6-month minimum, 1-2 days/wk embedded): continues operating the bundle end-to-end and coordinating with the adjacent measure-swarm-rollup, MMM, master-record-canonicalization, and call-tracking-integration skills.

Question 4

Who owns the receipt data, POS credentials, attribution model, and audit trail?

Accepted Answer

Operator owns 100% of every artifact. The receipt data sits inside the operator data warehouse (Snowflake, BigQuery, Databricks, Redshift, or Postgres). Per-vendor API, webhook, SFTP, and file-drop credentials for Square, Toast, Clover, Shopify POS, Lightspeed, Revel, Aloha, Micros, Oracle Symphony, NCR Counterpoint, TouchBistro, Talech, Vend, Erply, Heartland Retail, Cake, ParTech, Brink, Salido, Upserve, Bbot, Olo, DoorDash, Uber Eats, Grubhub, and the back-office stack sit under operator billing. The normalization mapping code lives in the operator repo with operator-controlled deploy pipeline. The visit-joining model code is aligned with the operator data-science team. The marketing-attribution model code is aligned with the operator marketing and finance teams. The compliance overlay rule library lives in the operator repo with attorney-approved updates and tracks HIPAA, DEA, Metrc, DISCUS, FDA tobacco, state licensing, PCI DSS, GDPR, CCPA, and state receipt-retention rules. The brand spec is versioned in the operator repo. LLM prompts live in the operator repo. The audit trail persists to operator-controlled storage with WORM retention where HIPAA, DEA, Metrc, or PCI DSS rules require it. Completions owns the orchestration knowledge — how to design the per-POS connector contracts, how to tune normalization, how to debug visit-joining cascades, and how to coordinate with the measure-swarm-rollup, MMM, master-record-canonicalization, and call-tracking-integration siblings. The operator can in-house at any time; Completions credentials revoke immediately on engagement-end.

Question 5

What does Completions commit to on a Tier 3 engagement?

Accepted Answer

Completions commits to a 6-workstream pre-engagement-baseline reporting cycle on the walk-in-phone-attribution agent: (1) Receipt-Ingestion workstream — pre-engagement baseline of which POS, ordering, and back-office vendors are connected today and which run via API vs webhook vs SFTP vs file-drop, then weekly reporting on per-vendor connector health and ingestion-cadence reliability. (2) Normalization workstream — pre-engagement baseline of canonical-schema coverage today across header, tender, line-item, discount, tax, tip, loyalty, payment-method, modifier, employee, station, shift, promotion, and comp dimensions, then weekly reporting on normalization coverage and schema-drift events caught vs missed. (3) Visit-Joining workstream — pre-engagement baseline of which of the nine signal sources are wired today and current join-confidence distribution, then weekly reporting on join-rate, confidence-tier distribution, and human-review queue depth. (4) Marketing-Attribution workstream — pre-engagement baseline of which of the 18 touch types and 10 attribution models exist today, then weekly reporting on attribution coverage and operator marketing-and-finance-team-aligned model output. (5) Compliance-Overlay workstream — pre-engagement baseline of which frameworks are attorney-approved today, then weekly reporting on overlay completeness, state-receipt-retention adherence where applicable, PCI DSS scope boundaries, and HIPAA/DEA/Metrc/DISCUS/FDA-tobacco persistence where applicable. (6) Connector-Maintenance + Cross-Agent workstream — pre-engagement baseline of per-vendor connector-health cadence today, then weekly reporting on vendor API changes detected, connector updates shipped, and coordination state with the measure-swarm-rollup, MMM, master-record-canonicalization, and call-tracking-integration siblings. Caveats: per-vendor API deprecations, schema changes, field renames, and field removals are POS-vendor decisions outside Completions control; per-vendor rate limits and outages are outside Completions control; attribution-model output depends on operator marketing-touch instrumentation upstream of the agent; incrementality-via-causal-uplift confidence depends on operator experiment design and budget; per-jurisdiction breach-notification windows, state receipt-retention rules, and PCI DSS scope changes require operator-counsel re-review; HIPAA, DEA, Metrc, DISCUS, and FDA-tobacco coverage applies only where the operator runs the relevant vertical POS; WORM-storage retention windows are operator-counsel-policy decisions; the audit trail persists to operator-controlled storage on the operator cloud account.

Question 6

How does engagement end and what is the operator transition path?

Accepted Answer

Tier 3 engagements are 6-month minimum with 90-day notice. At engagement end, Completions transitions back to operator in-house in 30-60 days: operating-playbook hand-off + in-house staff training across 3-5 operator team members covering receipt ingestion, normalization, visit-joining, marketing-attribution, per-vendor connector maintenance, and compliance-overlay management + receipt-data infrastructure hand-off + per-vendor credentials hand-off + normalization mapping code hand-off + visit-joining model code hand-off + marketing-attribution model code hand-off + LLM prompts hand-off + compliance overlay rule library hand-off + audit-trail hand-off with operator-account-ownership confirmation; Completions credentials revoke immediately on engagement-end.

Frequently asked