Universal Consumer Goods (UCG)

AI-Assisted Study Note

This page brings together public scenario links and AI-assisted research notes for study use. Start with the scenario brief, make your own attempt, and open the spoiler section only when you are ready to compare.

Scenario Snapshot

Field	Detail
Start here	Discovery index
Scenario source	Community scenario
Current status	Live
First public date	2021-02
Primary source	Open primary source
Coverage available	Scenario brief + Discussion or analysis

Why This Scenario Matters

• This entry is included because it appears in the public CTA scenario corpus and has enough public evidence to track for study use.

Only Open If You Have Attempted the Scenario

The section below contains public follow-up links, board-call material, and AI-assisted notes compiled from those public sources.

Open follow-up links, Q&A, and analysis

Follow-Up Links

• Discovery index
• Analysis reference

Board Insights & Common Pitfalls

Generalized Judge Questions

• Territory Management: “You chose a Private sharing model for Accounts. How will you ensure a Regional Manager can see all stores in their territory without using ‘View All’?”
• Mobile Performance: “Why did you choose Consumer Goods Cloud over a custom LWC mobile solution? How does your choice handle pricing calculations in a basement with no signal?”
• Order Synchronization: “Explain the end-to-end flow of an order from the mobile app to the legacy ERP. What happens if the sync fails while the rep is at the next store?”
• In-Store In-Stock: “If the ERP is down, how will your field reps know if a product is in stock? Did you consider local caching or priming of inventory levels?”
• LDV Store Visits: “You have 50M ‘Store Visit’ records per year. How will this impact report performance, and what is your specific mitigation strategy?”

Common Mistakes

• Over-Engineering Retail Execution: Proposing custom mobile apps or full FSL when Consumer Goods Cloud (CGC) is the standard, idiomatic choice for store visits.
• Sync Integration for Orders: Proposing a real-time synchronous callout for every order. This is a critical fail in low-connectivity retail environments; the correct pattern is Asynchronous (Fire & Forget).
• Ignoring Offline Pricing: Failing to explain how reps calculate complex discounts or promotions while offline at a retail site.
• License Misalignment: Assigning standard Sales Cloud licenses to all field reps when specialized CG Cloud licenses are required for retail execution objects.

Strong Patterns

• CGC Offline Priming: Leveraging the out-of-the-box offline sync capabilities of Consumer Goods Cloud to handle retail environments.
• LDV “Hot Data” Tiering: Keeping only the most recent 3 months of Store Visits in Salesforce and offloading the rest to Big Objects or Snowflake.
• Enterprise Territory Management (ETM): Using ETM to handle the complex, regional store assignment and visibility requirements.

Strategic Insights

• The “Retail Execution” Benchmark: UCG is often used as a 60-minute evaluation scenario. Success depends on being surgical: focusing on the “Core 5” objects (Account, Contact, Product, Order, Visit).
• Why over What: Judges in this scenario heavily weigh the justification for using (or not using) CG Cloud.

Additional Notes

• High-volume retail execution scenario focusing on store visits, field sales, and complex territory hierarchies.
• Often used as the standard scenario for the CTA Architect Evaluation.