Salesforce & Pardot WooCommerce POS — Oliver POS Integration Guide

Oliver POS doesn't have a partnership with Salesforce or Pardot. It supports both because the Salesforce Integration for WooCommerce plugin already syncs customers and orders from WooCommerce into Salesforce, and Pardot (now Marketing Cloud Account Engagement) reads from Salesforce. Oliver writes every in-store sale into WooCommerce as a normal order, the plugin syncs it to Salesforce as a contact + opportunity (or custom object), and Pardot picks up the change on its standard sync. Salesforce does the CRM. Pardot does the B2B marketing automation. WooCommerce is the system of record. Oliver is the till on top.

What Salesforce / Pardot is, exactly

Salesforce is the enterprise CRM standard, used by hundreds of thousands of businesses worldwide as the source of truth for contacts, accounts, opportunities, and pipeline. Pardot, since rebranded Marketing Cloud Account Engagement, is the B2B marketing-automation product that sits on top of Salesforce — running prospect scoring, Engagement Studio programs, and email campaigns against Salesforce contact and lead records.

The Salesforce Integration for WooCommerce plugin syncs WooCommerce customers and orders into Salesforce as configurable object mappings — typically contacts (or leads), opportunities, and custom WooCommerce-order objects. Pardot prospects mirror Salesforce contacts, so anything that updates a Salesforce contact via the WooCommerce sync also surfaces in Pardot.

How Oliver POS feeds in-store sales into Salesforce / Pardot

The Salesforce + Pardot WooCommerce POS flow inside Oliver:

1. The cashier rings the sale on the Oliver register and taps Charge.
2. Oliver prompts to attach a customer.
3. The cashier takes payment through whatever WooCommerce payment gateway the store uses.
4. Oliver writes a standard WooCommerce order.
5. The Salesforce plugin syncs the customer and the order on the schedule you've configured (real-time or batched). The Salesforce contact and the related opportunity or custom-object record update.
6. Salesforce process automation (workflow rules, flows, Apex triggers) fires on the update; Pardot picks up the change via its standard Salesforce sync and any scoring rule or Engagement Studio program referencing those fields fires the next time the prospect's record evaluates.

The Salesforce WooCommerce plugin — what Oliver rides on

Oliver rides on the Salesforce Integration for WooCommerce plugin. Setup follows Salesforce's standard integration playbook: install the plugin, authorize the connected app in Salesforce, configure the object mapping, and let the integration push WooCommerce data on a real-time or scheduled basis.

Why pushing in-store sales into Salesforce / Pardot matters

Enterprise retail teams expect the Salesforce contact record to be the canonical view of a customer. If in-store sales are missing, the canonical view is broken:

• Pardot scoring goes off track because the model assumes complete activity data.
• Account Engagement journeys fire against incomplete data and contact the wrong prospects.
• Account managers handling key wholesale or VIP accounts can't see what those accounts are actually buying when they walk into the flagship.
• Pipeline reports under-represent the business because opportunities are missing.

Push Oliver POS sales through WooCommerce into Salesforce and the contact record becomes accurate. Pardot scoring incorporates in-store purchase events; Engagement Studio programs branch correctly; account managers see counter visits on the contact timeline.

What this is NOT

Oliver POS is not a Salesforce or Pardot partner. There's no co-marketing agreement, no revenue share, and no special pricing. Oliver doesn't insert itself between WooCommerce and Salesforce; the data path is the same one any WooCommerce store uses. Oliver doesn't charge a markup or per-user fee. Your Salesforce org and Pardot account are entirely between you and Salesforce.

Setup in 4 steps

1. Install the Salesforce Integration for WooCommerce plugin and authorize the connected app in Salesforce.
2. Configure the object mapping (WooCommerce customer ↔ Salesforce contact/lead, WooCommerce order ↔ Salesforce opportunity or custom object).
3. Install Oliver POS, sign in to the register, and confirm the customer-capture prompt with marketing consent is enabled at checkout.
4. Run a small live test sale at the counter and confirm the contact and related record update in Salesforce within the configured sync interval, then verify Pardot reflects the change on its next sync.

FAQ

Does the sync support custom WooCommerce-order objects in Salesforce?

Yes. The Salesforce Integration for WooCommerce plugin lets you map WooCommerce orders to standard Salesforce objects (opportunities) or to custom objects you've defined for orders. Oliver POS sales follow the same mapping.

Can Pardot scoring reflect in-store purchases?

Yes — once Oliver POS sales reach Salesforce as updates on the contact record, Pardot picks up the change via its standard sync and any scoring rule referencing those fields fires the next time the prospect's record evaluates.

Does Oliver POS partner with Salesforce or Pardot?

No. Salesforce and Pardot are supported because the Salesforce Integration for WooCommerce plugin is an off-the-shelf integration any WooCommerce store can install.

Does Oliver charge extra to use Salesforce or Pardot?

No. Oliver's pricing is a flat monthly POS software fee. You pay Salesforce directly on Salesforce's published pricing.

Will my online + in-store customers be one Salesforce contact?

Yes. The plugin matches by email; Oliver POS attaches the WooCommerce customer to every register sale, so the shopper has one Salesforce contact spanning online and in-store activity.

Try Oliver POS free for 30 days at /demo/ — bring your WooCommerce store and your Salesforce org and unify your enterprise customer record within an hour.