Puma India

DraftLast checked Mon Oct 26Owner Param

Answer

PUMA India is the design partner that is one market's store of a global brand, on Salesforce Commerce rather than Shopify, so it tests Brew on a store that is not Shopify and a name with a market attached; it has a read and Plays and no connected accounts.

Today

Profile

Fact	Source
Slug `in-puma-com`, store in.puma.com	memory brew-live-stores brew/reader/index.js:90
Store platform Salesforce Commerce	memory feed-for-all-brands
"PUMA India" is also "PUMA" in AI answers, marketplaces and weekly checks	brew/CLAUDE.md:33 brew/reader/index.js:204
Reviews are switched off on the store	brew/reader/stages/reviews.js:19
Its image server refuses requests without a browser user agent	brew/reader/util.js:32
PUMA's own font is proprietary, so a fallback sans is used until they upload it	memory brew-jam-v2
A real design partner prospect; never wiped or reset	memory brew-live-stores
Home is production since 25 Oct	memory brew-prod-backend brew/deploy.sh:19-20

Connections

None brew/docs/audit-2026-10-24-design-partners.md:3

History

Date	What happened	Source
23 Oct	Wiped to start fresh, then read again	memory brew-live-stores
23 Oct	The rivals stage timed out on Puma; rivals now get a light 30 second price read	brew commit 1c61301
23 Oct	Studio tested live: an evoSPEED shot	memory brew-jam-v2
24 Oct	Shown "No live ads" because the tracker searched the store name, not the page "PUMA"; fixed for every brand	brew/docs/audit-2026-10-24-design-partners.md:12 brew/pack-numbers.js:39
24 Oct	The reading page once named it "In" from the address; fixed	brew/feed-service.js:229 brew/seed-template.js:46
25 Oct	Copied to production	memory brew-prod-backend brew/db/partner-copy.js:43

Open issues

A statics picture from 22 Oct has "PUMA India Product / Scuderia Ferrari Fanwear Baseball Cap" drawn in it; the maker is not traced brew/docs/audit-2026-10-24-design-partners.md:26

Next step

None on record. See Open.

Tomorrow

Item	Version	Tag
The brand's base name and market name both count as the brand everywhere	v1	Stays
A brand font upload, so made pieces use PUMA's own type	v1	New, proposed
A non Shopify store connection, or GA4 first	v1	New, proposed

How we do it

Before any reader change ships, check it on PUMA India as the non Shopify, big catalogue case.
Trace the statics maker that drew words into a picture before showing PUMA any statics again.
Follow the onboarding playbook; the store step is GA4, not Shopify.

Numbers

Metric	Definition	Where measured	Status
Team members	People from the brand's email domain who joined	`private/members.json`	Proposed
Connected accounts	Real accounts reading	Connector ledger	Today: 0
Pictures with stray words	Statics or drafts with words drawn in that the brand did not write	Look judge and audit	Proposed

Open

Who at PUMA India is the contact, and who approves the use of PUMA's name on our side? Proposal: record the contact here and ask in writing before PUMA appears in any demo, deck or case study.
Should a brand this big be a design partner? Proposal: keep it as the big brand test case, and never quote it as a customer until it says yes in writing.
Do we fix the stray words picture first? Proposal: yes, trace the maker before PUMA's next session.

Sources

brew origin/main a559de6: CLAUDE.md:33, db/partner-copy.js:43, deploy.sh:19-20, reader/index.js:90 and 204, reader/stages/reviews.js:19, reader/util.js:32 and 65-86, seed-template.js:46, feed-service.js:229 and 2438, pack-numbers.js:39, research.js:480, docs/audit-2026-10-24-design-partners.md
brew commit 1c61301
memory: brew-live-stores, brew-prod-backend, feed-for-all-brands, brew-jam-v2, brew-read-stream-backfill

Source file content/sales-and-partnerships/puma-india.md · For agents: Markdown · JSON