Food Trucks R Us (FTRU)

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-06
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

• LDV Check-ins: “How will you handle the millions of daily ‘Check-ins’ from food trucks? Why choose Platform Events for real-time updates over standard object storage?”
• Person Accounts Logic: “Why did you choose Person Accounts for the massive B2C truck customer base? What are the integration trade-offs compared to a standard Account/Contact model?”
• Mobile Connectivity: “Food trucks operate in areas with spotty internet. How does your solution support offline order taking and synchronization? Explain the Briefcase configuration.”
• Moving Personas Security: “How do you ensure Truck Owner A cannot see sales data for Truck Owner B when trucks frequently move across regions? Is a static Role Hierarchy sufficient?”
• Identity for Drivers: “How are you authenticating third-party delivery drivers? Which OAuth flow is used for their mobile app access?”

Common Mistakes

• GPS Storage Bloat: Attempting to store every high-frequency GPS ping in standard Salesforce objects, leading to immediate locking contention and storage failure.
• Ignoring Offline Briefcase: Failing to specify the Mobile Offline/Briefcase Builder requirements for field-service style operations in remote locations.
• Driver Over-licensing: Assigning full Sales Cloud licenses to external contractors (drivers) when External Apps or CC+ is the more cost-effective “sweet spot.”
• Account Data Skew: Parenting all food trucks under a single regional “City” Account, creating a massive parent-child skew that blocks record locking.

Strong Patterns

• Virtual Account Buckets: Using a “Bucket” strategy or Virtual Accounts to distribute the load of millions of B2C customers and prevent data skew.
• LWC/Mobile SDK for High-Perf: Choosing a custom LWC or Mobile SDK solution for the courier/driver experience to handle the complex offline QR scanning and POS integration.
• Criteria-Based Sharing: Leveraging dynamic sharing based on truck status/location rather than a rigid geography-based role hierarchy.

Strategic Insights

• The “Field Service” Hybrid: FTRU tests the architect’s ability to borrow Field Service patterns (scheduling, routing, offline) without necessarily requiring the full FSL license suite.
• Order SoR: Success depends on being extremely clear about the “Source of Truth” for Orders (Salesforce vs. an external POS system).

Additional Notes

• Focuses on mobile-first, high-volume B2C/B2B logistics, real-time location tracking, and POS integration.