Clover items are matched to Acumatica inventory items by SKU in the Biz-Tech Services Clover Connector. The product page says a visible cross-reference shows which records are linked and which need review. It also says Clover items can create Acumatica records, while Acumatica items can be published to Clover with a description, price, and category. Those options make a clean SKU list and a deliberate owner for item changes essential before a full catalog is connected.
The published product description confirms the capabilities above, but does not name a mapping screen, exact field labels, duplicate-SKU behavior, or an automatic resolution rule. Treat the checks below as an implementation checklist to test in your own configuration.
What an Item Link Has to Support
The Clover Connector brings register sales into Acumatica as invoices or sales orders. The published description says each resulting document has a line for every item sold, at the price charged at the register. It also carries the sale’s discount, service charge, tip, and tax. For the item line to be useful in inventory and reporting, the SKU relationship must point to the intended Acumatica item.
The connector’s cross-reference is the place the product page tells operators to distinguish linked items from records needing review. That is a narrower claim than assuming every incoming SKU is safe to import. A visible link should be checked against the product, unit, and selling context before it is accepted for production transactions.
Clover SKU Mapping at a Glance
Use this sequence as a controlled rollout, rather than turning on the full catalog at once:
- Export or review the current Clover item list and the Acumatica item list. Identify the SKU value each system uses for the same product.
- Separate one-to-one SKU matches from missing, duplicate, and ambiguous values. Assign an owner to resolve each exception.
- Review the connector’s visible cross-reference. Confirm the intended Clover item points to the intended Acumatica record.
- Decide whether an unmatched Clover item should create a new Acumatica record or wait for a catalog owner to create and approve one.
- Run a small sale through the connector’s pull and import steps. Check the item line, charged price, discount, tip, tax, and resulting document.
- Publish or synchronize a small set of approved items, then verify description, price, category, and stock figures at the register before widening the scope.
The product page documents SKU matching, item creation, item publishing, two-step sale import, and quantity export. It does not prescribe this exact rollout order. The sequence is an editorial recommendation for validating those documented functions.
Clean the Catalog Before Matching
Start with records that a person can identify without guessing. For each SKU, note the item name, the intended Acumatica inventory record, and whether the item should be sold at the register. A blank SKU, reused code, or code assigned to different products needs a decision before the cross-reference is approved. The published Clover page does not say how the connector handles those cases.
Keep duplicate handling in the project record: which product keeps the code, which product gets a new code, and who authorizes the change. If multiple Clover records seem to point to one Acumatica item, confirm whether that is intentional in a test transaction. Do not assume the connector merges or rejects them automatically; no such rule appears in the product description.
Catalog cleanup is also where the team chooses a direction for new items. The connector can create Acumatica records from Clover items and publish Acumatica items to Clover. Decide who approves a new record and which system provides its description, price, and category. Otherwise, a mapping review can become an accidental item-master change.
Review the Cross-Reference and Unmatched Items
The visible cross-reference is useful because it exposes links that exist and links still needing review. Check it before importing a batch of register sales or publishing more products. For each sampled record, compare the Clover SKU with the intended Acumatica inventory item, then verify the item used on an imported document line.
The product page does not give a named unmatched-item queue, a screen ID, or a specific error message for an unknown SKU. It does say sales are pulled and imported in two deliberate steps, which gives an operator a chance to review before posting and retry a sale that needs attention. Record what an unmatched item does in a test sale, including any message and whether the document remains unposted. That result is more useful than guessing from a generic integration pattern.
Set Ownership for Item, Price, and Stock Changes
Item mapping is a business decision as well as a connector setting. The official description supports two item directions: Clover items can create Acumatica records, and Acumatica items can publish to Clover with description, price, and category. Choose an approval path for each direction and document who changes an existing item when the two catalogs disagree.
Stock has a more explicit owner. The product page calls Acumatica the source of truth for quantities. A business can choose on-hand, available, or available-for-shipping quantity and can draw it from one warehouse or the whole company. Confirm that choice before publishing quantities to Clover. The connector shows the quantity Clover holds and when it was last sent, which gives the team a check after the export.
Test a Small Transaction Set Before Expanding
A mapping that looks right in a list still needs a transaction test. Include a normal sale, a sale with multiple items, and a known exception. The documented import creates an Acumatica invoice or sales order with an item line for each Clover item sold. Compare those lines with the Clover receipt, including the price charged, discount, service charge, tip, and tax. The page says sales can be reviewed between pull and import, and retried when attention is needed.
Returns deserve a separate check. The connector description says a register refund becomes an Acumatica credit memo against the original invoice and carries returned lines, discounts, and tax. Verify that the returned item is the same item that appeared on the sale. Then check one approved item published from Acumatica to Clover and one inventory quantity export. Only after these examples reconcile should the team expand the connected catalog.
Where to Check Your Work
- Compare the visible Clover-to-Acumatica cross-reference with the approved SKU list; note links that still need review.
- During the two-step sale import, inspect a sampled sale before posting and retry any sale that needs attention.
- On the resulting invoice or sales order, compare each imported item line and charged price with the register receipt.
- For a return, compare the credit memo’s returned lines with the original invoice and refund.
- After an item publish, check its description, price, and category in Clover.
- After quantity export, check the quantity Clover holds and the recorded last-sent time against the chosen Acumatica quantity basis.
Clover Item Mapping: Frequently Asked Questions
What does the Clover Connector use to match products?
The Biz-Tech Services product page says products are matched on SKU and that a visible cross-reference shows linked items and items needing review. It does not specify additional identifier precedence.
Can an unmatched Clover item create an Acumatica record?
The page says Clover items can create Acumatica records. It does not publish the exact conditions, defaults, or approval controls. Test the behavior and assign an item owner before enabling it for a broad catalog.
What happens when two Clover products share a SKU?
The published description gives no duplicate-SKU rule. Resolve the duplicate in the source catalog or verify the configured behavior with a controlled test before importing those products.
Does the connector show items that still need review?
Yes. The product page says the visible cross-reference shows what is linked and what still needs review. It does not give the screen name or a separate unmatched-item queue.
Which system owns the stock quantity shown in Clover?
The page identifies Acumatica as the quantity source. The business chooses the quantity basis and whether to use one warehouse or the whole company.
How can I tell whether a test sale used the right item?
Compare the Clover receipt with the imported Acumatica invoice or sales order. Check each item line and price, then review any discount, service charge, tip, and tax recorded on the document.
Keep the SKU Link Reviewable
A workable Clover item map has an approved SKU list, a reviewed cross-reference, an owner for new and changed records, and test transactions that match the register receipts. The connector’s documented two-step import and visible links give the team places to check its work. Screen names and duplicate-handling rules still need confirmation in the installed configuration.
For a review of Clover catalog mapping and transaction tests in Acumatica, contact Biz-Tech Services at https://biz-techservices.com.
Source: Biz-Tech Services, Clover Connector product page, https://biz-techservices.com/clover-connector (accessed October 26, 2026).
