3PL QA Runbook
Vesper QA guide for provider configs, runtime schedules, sales order fulfillment sync, inventory mirror, tracking, warehouse handoff, and recovery validation
Use this runbook in Vesper QA only:
https://exodus--vesper.sandbox.lightning.force.com
QA Scope
Run 3PL QA when changing provider configs, runtime settings, sales order sync, purchase order sync, inventory mirror, tracking, warehouse handoff, provider credentials, runtime scheduling, or fulfillment dashboards.
Preconditions
| Requirement | Expected QA behavior |
|---|---|
| Provider references | Use existing Pakmo/Kandy Kush-style provider references when the runbook or E2E data model calls for them. |
| Target org | Use vesper for Salesforce CLI commands. |
| Test orders | Use generated QA orders and labels. |
| Provider data | Use sandbox provider accounts/configs only. |
| Cleanup | Keep run labels, manifests, and evidence with the run. |
Provider Config Check
- Open the 3PL Management app.
- Review
ThreePL_Provider_Config__crecords for the target warehouse/provider. - Confirm provider account references.
- Confirm sales order, purchase order, and inventory sync toggles.
- Confirm runtime windows, operating days, and time zone.
- Confirm endpoint extensions and lookback windows.
- Confirm last connection status and error fields.
If a configured provider warehouse must be replaced, use the successor-backed warehouse handoff path.
Runtime Settings Check
- Open 3PL Runtime Settings.
- Confirm scheduler status and scheduler owner.
- Confirm runtime user fields and last setup check.
- Confirm fulfillment failure alert toggle and cooldown.
- Confirm last request processed time moves after runtime work.
Do not assume runtime is active from class metadata alone.
Sales Order Fulfillment Sync
- Create or use a QA Sales Order with provider-routed items.
- Confirm item source refs and warehouse/provider routing.
- Confirm eligibility and order state.
- Trigger or wait for runtime sync as appropriate for the test.
- Inspect runtime request, transaction, sync state, and fulfillment sync history.
- Confirm provider-side order state when available.
- Confirm Salesforce Sales Order status and line fulfillment state.
Expected evidence includes ThreePL_Runtime_Request__c, ThreePL_Transaction__c, ThreePL_Record_Sync_State__c, Fulfillment_Sync_History__c, and Sales Order line state.
Inventory Mirror QA
Provider-owned inventory should be mirrored from the provider.
- Confirm item/warehouse rows exist in
Inventory__c. - Confirm provider source system and remote/source reference.
- Confirm provider snapshot time and mirror status.
- Confirm Stock Lookup shows the expected availability signal.
- Do not manually adjust provider-owned inventory to fix a mirror issue.
For internal warehouse stock, use Inventory Manager and confirm Inventory_Transaction__c history.
Tracking QA
- Confirm provider shipment/tracking data is available or use a safe QA tracking update.
- Confirm
Sales_Order_Tracking__cis created or updated. - Confirm tracking appears on the Sales Order.
- Send tracking email from Salesforce only after confirming the record is accurate.
- Confirm email history and recipients.
If tracking exists externally but not in Salesforce, re-pull provider state before manually adding tracking.
Purchase Order Sync QA
When PO sync changes:
- Use Purchase Order Pipeline to create or select a QA PO.
- Confirm provider routing and warehouse.
- Sync to provider if enabled.
- Receive/update through provider or Salesforce test path.
- Confirm received lines, inventory effect, PO status, and notification state.
Warehouse Handoff QA
Warehouse/provider replacement requires:
- Source warehouse and provider config.
- Successor warehouse/config.
- Inventory blocker review.
- Open order blocker review.
- Provider transition record.
- Post-handoff routing validation.
- Dashboard/report check.
Do not call handoff safe if open orders or inventory blockers remain unresolved.
Recovery QA
| Failure | Validation |
|---|---|
| Provider auth failure | Confirm provider account/credential state and error reporting. |
| Runtime request retry | Confirm retry state and no duplicate order side effects. |
| Tracking omitted | Re-pull provider state and confirm tracking row update. |
| Inventory stale | Confirm poll schedule, last success/error, and mirror timestamp. |
| Fulfillment failed | Confirm fulfillment failure alert, cooldown, and operations visibility. |
Exit Criteria
3PL QA is complete when:
- Provider config and runtime settings are verified.
- Sales Order sync evidence exists.
- Provider state and Salesforce state agree or differences are documented.
- Tracking and customer email behavior are verified if changed.
- Inventory mirror behavior is verified if changed.
- Dashboards/reports show no new critical issues.
- Cleanup/evidence is attached to the run.
Last updated on