Connect Salesforce with Revel Systems to sync in-store POS sales, customers, and product data into CRM, improving reporting, segmentation, and service across channels.
• Revel transactions are exported to Salesforce as orders and order line items, with tenders, taxes, and discounts mapped to dedicated fields.
• Customer profiles are matched using stable identifiers (email, phone, or POS customer ID), with merge rules controlling record ownership when duplicates appear.
• Product, price, and SKU references are mapped between Revel item IDs and Salesforce product catalog records to keep order lines consistent.
• Location and register context is mapped to Salesforce stores or business units, supporting multi-store reporting and territory-based access.
• Syncs run as scheduled batches and/or event-driven jobs where available, with delta logic sending only changed records to reduce payload size.
• Validation and error handling route failed records to retry queues, while sync logs capture payloads, timestamps, and mapping exceptions for auditability.
.png)
We map Revel sales, items, tenders, and customer identifiers into Salesforce objects, then sync on a schedule or near real time via API or middleware. You get consistent purchase history for segmentation, service follow-ups, and loyalty.
Yes – we can sync products and price lists from your source of truth and push updates to the other system with location-level rules. This helps avoid SKU drift, pricing mismatches, and reporting gaps across stores.
Most teams sync transactions, line items, discounts, refunds, customers, store locations, and staff IDs. We also align UTM or campaign IDs where available, so Salesforce reporting reflects what actually drove revenue.
It can, as long as return events are modeled explicitly and tied back to the original sale. We set up return and adjustment logic so lifetime value, net revenue, and customer status stay accurate.
scandiweb delivers the integration end to end, including data modeling, API work, QA, and monitoring, and we can support ongoing changes post-launch. With 2,100+ projects delivered since 2003, we’re used to integrations that evolve as you add stores, channels, and workflows.





