What This Feature Does
Sync Audit compares your product and sales data across every system you’ve connected — NetSuite, Shopify, NewStore, and Comestri — and surfaces anything that doesn’t line up. Instead of discovering a pricing mismatch when a customer complains, or a missing product when a sale fails to process, ItSynx checks for these problems and puts them in front of you before they become customer-facing issues.
These are two related features working the same way:
- Sales Audit — checks that sales exist and match in value between systems.
- Product Audit — checks your product catalogue for consistency between systems.
This guide covers:
- Where to see audit issues at a glance (your Dashboard)
- The full Sync Audit pages, and how they’re organised
- What each validation rule actually checks for
- Drilling into an issue to see the affected records, and exporting them
- How the colour-coded warnings work
- Keeping counts up to date
- Getting audit alerts by email, or in a shared Slack or Microsoft Teams channel
Before You Start
The systems you want to audit need to be connected to ItSynx first. See the Getting Started guide.
Which Checks You See
Audit is configured per connected system, so what you see depends on which systems your team has connected and enabled it for. If you don’t use Comestri, for example, you won’t see any Comestri-related checks — there’s nothing to hide; the checks simply don’t apply. Many checks also only appear once both systems being compared are enabled (there’s no point checking a NetSuite product against Shopify if Shopify auditing isn’t switched on).
Where You’ll See It
Dashboard
Your Dashboard is the fastest way to know whether anything needs attention:
- The Product Audit card includes any product issues alongside your catalogue’s general health (unpublished counts, UPC availability). Only issues that actually have something to show appear here — a quiet dashboard means nothing needs attention.
- The Sales Audit card lists any sales issues found, e.g. “Shopify sales that do not exist in NetSuite”. If everything checks out, it simply shows All sales are reconciled across your systems.
When something needs attention, each card leads with how many checks need attention and lists them beneath. The foot of each card shows when it was last updated, with a refresh icon to force a live recount instead of relying on the cached figure.
Sync Audit Pages
For the full picture, visit Product Audit from the Products menu or the Sales Audit from the Sales menu. This shows every validation rule configured for your team, grouped by which system’s data is being validated (e.g. “NetSuite Validation Rules”, “Shopify Validation Rules”). Each rule shows its status and a live count, colour-coded the same way as the Dashboard, and each group has its own refresh button. A rule with nothing to report shows Matched. Otherwise it shows what it found: Missing, Mismatch, Duplicate or Invalid.
Click any rule to open the underlying list of affected records.
Product Audit — What’s Checked
Depending on which systems you have connected, you may see checks such as:
Comestri
- Products that don’t exist as an active item in NetSuite (Gift Cards are excluded, since they’re not expected to)
- Duplicate Comestri products
NetSuite
- Products that don’t exist in Comestri or NewStore, but have pricing set (a strong sign the product should have been published there)
- Duplicate External IDs
- Duplicate UPCs
- Products missing their UPC attribute entirely
NewStore
- Products that don’t exist as an active item in NetSuite (again, excluding known Gift Cards)
- Duplicate NewStore products
- In-stock products with an invalid HS Code (a customs/compliance risk for shipping)
Shopify
- Products that don’t exist as an active item in NetSuite (SKU matching ignores differences in letter case and accents)
- Products whose sale price doesn’t match the resolved NetSuite price
In every “doesn’t exist in NetSuite” check, a product that matches only an inactive NetSuite item is listed as missing, because it can’t be sold through NetSuite.
Sales Audit — What’s Checked
NewStore
- Sales that don’t exist in NetSuite
- Sales whose dollar value doesn’t match NetSuite
Shopify
- Sales that don’t exist in NewStore or NetSuite
- Sales whose dollar value doesn’t match NewStore or NetSuite
A small tolerance is applied when comparing sale values, so trivial rounding differences between systems aren’t flagged as errors.
Allowing Time for Sales to Arrive
Where your team has processing allowances configured, missing-sale checks give orders time to reach the next system before reporting them. The allowance is assessed as of the latest successful import from that destination, not the current time. A sale is reported as missing only when its allowance had elapsed before that import began and no matching destination record was imported. Simply waiting or refreshing the page does not make more sales overdue.
Shopify allowances start from payment completion, not initial order creation. An order created earlier but paid recently therefore receives the full processing allowance from payment.
Processing allowances are practical estimates of reasonable processing time, not contractual SLAs. They are configured individually for each team and destination system. ItSynx staff can adjust your team’s allowances as needed; contact support to discuss your settings or request a change. Teams without configured allowances retain the existing checks.
The audit compares the latest data imported into ItSynx, rather than checking each system live. A later successful import may therefore add or clear missing-sale results. Failed imports do not move the assessment time forward. Where allowances apply, missing-sale results are not shown until the destination has been imported successfully at least once; an empty list alone does not confirm that imports are up to date. Refreshing an audit count rechecks the imported data; it does not trigger a new import. Sale-value mismatch checks are unchanged by these allowances.
Investigating an Issue
Clicking through from either the Dashboard or the Sync Audit page opens a searchable, sortable, paginated table of the affected records — for example, every Shopify order whose total doesn’t match its NetSuite equivalent, side by side with both values and currencies.
From here you can:
- Search and sort to narrow down to a specific record or pattern.
- Export the full result set to CSV using the Export button, useful for sharing with a teammate or investigating in a spreadsheet.
Resolving the underlying issue in the source system (correcting a price, creating a missing record, fixing a duplicate) is what clears it — ItSynx surfaces the problem, but the fix happens wherever the data actually lives.
After correcting a sale, allow the next scheduled sales import to complete before refreshing the audit. Refreshing the count alone does not retrieve the correction from the connected system.
Understanding the Colour-Coded Warnings
Every check shows as:
- Green — nothing to worry about (zero results, or below the rule’s normal threshold).
- Amber — some results found and worth a look.
- Red — enough results to need attention soon.
The exact thresholds vary by rule. Checks like “does not exist in another system” tolerate a handful of results before turning red, since a few are often expected during normal day-to-day activity. Checks like a price or sale value mismatch turn red as soon as a single result is found, since even one is worth investigating straight away.
Keeping Counts Up to Date
Counts are cached for a few minutes so pages load quickly. Use the refresh icon on any Dashboard card or Audit group to force an immediate recount if you’ve just fixed something and want to confirm it’s cleared.
Audit Alerts
Audit alerts email you when a check you care about has errors, so you don’t have to keep checking.
Subscribing to a check
On the Product Audit or Sales Audit page, select Subscribe beside any check. Tick Email me, enter the error count that should trigger an alert, for example 10 if a few errors are normal for that check, then select Save. The check then shows Subscribed ✓.
You can only subscribe to checks you can see, and each subscription is for your current team. If you belong to several teams, subscribe in each one separately.
When you’ll get an email
ItSynx checks your subscribed checks automatically after the data they compare has been imported. You don’t need to open the page.
- You get an email when the error count is at or above your number and the affected records have changed since your last alert.
- While the same errors remain, you get a reminder once a day.
- Nothing is sent while the count is below your number, and nothing is sent when errors clear.
- If an import hasn’t completed successfully, ItSynx doesn’t send a result based on incomplete data. Reminders say when the check last ran.
Each email names the check, the current count, and when the data was last imported, with a link straight to the affected records. Emails never include the records themselves.
Changing or stopping alerts
Select Subscribed ✓ beside the check to change your number, or untick Email me and select Save to unsubscribe. You can also unsubscribe using the link at the bottom of any audit alert email, without logging in.
If you lose access to a check, for example because your role changes, your subscription to it is removed automatically.
Posting alerts to a Slack channel
Team members who can manage team settings can also post audit alerts to one shared Slack channel for the team. This works alongside email alerts; it doesn’t change anyone’s personal subscriptions.
Important: everyone in the Slack channel sees these messages, including people who don’t use ItSynx. Messages show only the team and check names, the number of affected records, when the check last ran, and a link to ItSynx. They never include the records themselves. Opening the link still requires an ItSynx login with access to that check.
Connecting Slack
- Open your team menu and select Audit Alert Channels.
- Select Add to Slack. Slack asks you to approve the ItSynx Audit Alerts app and to pick the channel to post to.
- After you approve, you return to ItSynx, which shows the connected channel.
Your Slack workspace administrators may need to approve the ItSynx Audit Alerts app before you can add it. To post to a different channel later, select Reconnect and pick the new channel; your chosen checks stay the same.
Choosing which checks post to the channel
On the Product Audit or Sales Audit page, select the alert button beside a check. Tick Post to #your-channel, enter the error count that should trigger a post, then select Save. The button then shows a # symbol. You can tick Email me in the same dialog too: email and Slack are independent, each with its own number. To change the number or stop posting, open the dialog again, change the number or untick the channel, and select Save. The Audit Alert Channels page lists every check that posts to the channel.
The channel follows the same rules as email alerts: a post when the error count reaches your number and the affected records have changed, a daily reminder while the same errors remain, and nothing when errors clear.
If Slack stops accepting messages
If the channel is deleted or archived, or the app is removed from Slack, ItSynx stops posting and shows a warning on the Audit Alert Channels page and in the alert dialog. Select Reconnect to choose a channel again. Email alerts are not affected.
To stop using Slack, select Disconnect on the Audit Alert Channels page. This removes the checks chosen for the channel. To remove the app from your Slack workspace as well, select Manage in Slack.
Posting alerts to a Microsoft Teams channel
Team members who can manage team settings can also post audit alerts to one shared Microsoft Teams channel, using a Teams workflow. A team can use a Slack channel and a Microsoft Teams channel at the same time, each with its own checks and numbers.
The same visibility rules apply: everyone in the Teams channel sees the messages, including people who don’t use ItSynx, and messages never include the records themselves.
Connecting Microsoft Teams
- Open your team menu, select Audit Alert Channels, then select Connect Microsoft Teams.
- In Microsoft Teams, open the channel’s More options (⋯) menu and choose Workflows.
- Choose the Send webhook alerts to a channel template, pick the team and channel, then select Save.
- Copy the workflow URL that Teams shows.
- Back in ItSynx, enter a channel name (for example, “Operations › Alerts”) so you know where alerts go, paste the workflow URL, and select Connect.
ItSynx sends a test message to the channel and connects only if Microsoft Teams accepts it. Check that the test message appeared in the channel.
Treat the workflow URL like a password: anyone who has it can post to the channel. ItSynx never shows it again. To change the channel or replace the URL, select Reconnect and enter both again; your chosen checks stay the same.
Tip: a Teams workflow belongs to the person who creates it, and stops running if that person leaves your organisation. Create it from a shared or long-lived account, and add a co-owner in the Workflows app.
Choosing which checks post to the channel
This works the same way as Slack: select the alert button beside a check, tick Post to your Teams channel, enter the error count, and select Save. If both channels are connected, the dialog shows each one separately.
If messages stop appearing
If the workflow is deleted or turned off, ItSynx stops posting and shows a warning on the Audit Alert Channels page and in the alert dialog. Select Reconnect and paste the URL of a working workflow.
Microsoft Teams accepts messages before the workflow runs, so some problems (for example, the workflow’s owner losing access to the channel) don’t reach ItSynx. If messages stop appearing without a warning, check the workflow’s run history in the Teams Workflows app.
To stop using Microsoft Teams, select Disconnect on the Audit Alert Channels page. This removes the checks chosen for the channel. ItSynx can’t delete the workflow, so turn it off or delete it in the Teams Workflows app as well.
Frequently Asked Questions
Why don’t I see any Comestri (or NewStore, or Shopify) checks?
Auditing is only shown for systems your team has connected and enabled it for. If a system isn’t in use, or auditing hasn’t been switched on for it, its checks simply won’t appear.
Does resolving an issue in ItSynx clear it?
No — ItSynx only reports what it finds. The underlying data has to be fixed in whichever system is wrong (or missing the record), and the count will clear the next time it’s checked.
Why did a count I just fixed still show the old number?
Counts are cached briefly for performance. Use the refresh icon to force a live recount.
Is this the same as the product health information on the Product Audit card?
Not quite — product health (unpublished products, UPC availability) is part of Product Management. Auditing checks are shown alongside it on the same card for convenience, but they’re validating different things: catalogue health is about your ItSynx-managed products, auditing is about consistency between systems.
I subscribed to a check but haven’t received an email. Why?
Alerts are only sent when the error count is at or above your number, after the data the check compares has been imported successfully. If the count is below your number, or nothing has changed since your last alert and a day hasn’t passed, there’s nothing to send.
An audit alert link asked me to switch team. Why?
The alert belongs to a different team from the one you currently have selected. Switch to that team to view it.
I selected Open in ItSynx in Slack or Microsoft Teams but couldn’t see the check. Why?
Channel messages are shared with the whole channel, but ItSynx only shows a check to people with access to it. If you can see the audit page but not that check, ItSynx opens the audit page instead. If you can’t see either, ask your team administrator about your role.
Why can’t I see Audit Alert Channels in the team menu?
Only team members who can manage team settings can connect Slack or Microsoft Teams and choose the checks that post to them.
ItSynx says my Teams webhook has been switched off. What should I do?
Microsoft has retired the older Teams webhooks (Incoming Webhook connectors). Create a new workflow with the steps in “Connecting Microsoft Teams” above and paste its URL instead.