Search documentation...

K
ChangelogBook a demoSign up

PAR Retail Stuzo Open Commerce

Stuzo helps Convenience & Fuel Retailers Know and Activate more customers and data in real-time, leading to more visits, more gallons, and bigger baskets.

Supported syncing

TypeDescriptionSupported Sync Modes
SegmentsSync data from any source to PAR Retail segmentsAdd, Remove
EventsSync data from any source to track loyalty points in PAR RetailInsert

For more information about sync modes, refer to the sync modes docs.

Connect to PAR Retail Open Commerce

Go to the Destinations overview page and click the Add destination button. Select PAR Retail Open Commerce and click Continue. You can then authenticate Hightouch to PAR Retail Open Commerce.

Enter the following fields into Hightouch:

  • API key: Assigned by Open Commerce and used to identify the communicating application
  • Client ID: Shared by Open Commerce and used to generate an auth token
  • Client secret: Shared by Open Commerce and used to generate an auth token

Sync configuration

Once you've set up your PAR Retail Open Commerce destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the PAR Retail Open Commerce destination you want to sync to.

Syncing segments

Sync data from any source to PAR Retail Open Commerce segments

Record matching

To match rows from your model to segments in PAR Retail Open Commerce, you need to select the model column that contains values that match the Membership UUID field. Refer to the record matching docs for more information.

Field mapping

Hightouch lets you sync segment fields via field mapping. You can map data from any of your model columns to the default segment fields. Ensure your model's columns have the same data types as the fields you want to sync to.

Split retries

PAR Retail Open Commerce counts all segments in a batch as rejected if the request contains a single invalid segment. To pinpoint which segments are getting rejected with which errors and reduce the number of valid segments that get retried, you can enable split retries.

Syncing events

Sync data from any source to track loyalty points in PAR Retail Open Commerce

To ensure syncs send each event, your event model must use a truly unique primary key. See the events syncs documentation for more information.

Record matching

You can match rows from your model to events in PAR Retail Open Commerce on any column in your model and any field in PAR Retail Open Commerce. Ensure the data types of the model column and PAR Retail Open Commerce field you select match. Refer to the record matching docs for more information.

Field mapping

Hightouch lets you sync event properties via field mapping.

Tips and troubleshooting

Common errors

To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.

Live debugger

Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.

Sync alerts

Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.

Ready to get started?

Jump right in or a book a demo. Your first destination is always free.

Book a demoSign upBook a demo

Need help?

Our team is relentlessly focused on your success. Don't hesitate to reach out!

Feature requests?

We'd love to hear your suggestions for integrations and other features.

Last updated: Nov 2, 2024

On this page

Supported syncingConnect to PAR Retail Open CommerceSync configurationSyncing segmentsSyncing eventsTips and troubleshootingCommon errorsLive debuggerSync alerts

Was this page helpful?