Universal Parcel Lockers (UPL)

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	Scenario brief PDF
Scenario source	Community scenario (Jakub Stefaniak)
Current status	Live (FR)
First public date	2021-01
Primary source	Open primary source
Coverage available	Scenario brief + Video or presentation + Public Q&A + Discussion or analysis

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

Board Insights & Common Pitfalls

Generalized Judge Questions

Org Strategy & Localization: “You chose a Single Org strategy for 10 countries. How will you handle different data formats for locker locations (Lat/Long vs. Locker ID) without polluting the global model?”
Mobile Conflict Resolution: “How do you handle ‘Conflict Resolution’ when a courier scans a parcel offline, but the sender cancelled it online seconds before?”
LDV History UX: “You mentioned Big Objects for the 5-year history. How will you display that data to a Customer Community user with performant filtering?”
State Machine Integrity: “Describe the technical flow of the QR code scan. How do you ensure the ‘No Cancellation’ rule is enforced immediately across the Mobile SDK and Salesforce?”
License Justification: “Why recommend Customer Community Plus? Could you have achieved the sharing requirements using standard Customer Community with Sharing Sets?”

Common Mistakes

Standard App Misuse: Suggesting the standard Salesforce Mobile App for high-frequency courier operations. Offline QR scanning usually requires a Native/Mobile SDK approach.
Sync Integration Traps: Using synchronous Apex callouts for parcel registration. If the Shipping System is down, the core ordering flow breaks.
Data Retention Oversights: Keeping years of tracking data in standard objects. At 150 parcels per month per pick-up point, this object hits 100M+ records quickly.
Missing Billing Logic: Overlooking the specific billing rules for “additional visits” or “extra parcels” mentioned in the logistics requirements.

Strong Patterns

Parcel State Machine: Clearly defining the status transitions (Draft -> Registered -> Scanned -> In Transit -> Delivered) across systems.
Platform Events for Decoupling: Using Platform Events to notify the Shipping System of new parcels, ensuring a resilient, asynchronous pattern.
Account Role Optimization (ARO): Required for managing the 400,000+ Pickup Point Managers to avoid hitting role limits.

Strategic Insights

The “High-Volume Identity” Test: UPL probes the architect’s ability to handle 25M recipients (who should be Guests, not Contacts) vs. 400k Managers (who need Community licenses).
Logistics Latency: Success depends on justifying the choice between Mobile SDK (high performance/offline) and Mobile Publisher (low cost).

Additional Notes

This scenario focuses on the transition from B2B (Senders) to B2C (Recipients) and the logistics of shared physical assets (lockers).

Always verify against official Salesforce documentation

This content is study material for CTA exam preparation. Content compiled and presented with AI assistance. Not affiliated with Salesforce.

Personal study notes for the Salesforce CTA exam. Content compiled from VJ's study notes, official Salesforce documentation, community sources, and online publicly available content, then organized and presented with AI assistance. Not affiliated with Salesforce. © 2025–2026 VJ Srivastava.