Hi,
I am creating template items in Acumatica using the bidirectional Shopify sync. However, when importing a new template item from Shopify, the Shopify tags are not being imported as Sales Categories in Acumatica.
Is there an option or mapping available to import Shopify tags into Acumatica Sales Categories? If this is supported, could you please advise on the required configuration?
Best answer by Saikrishna V
Steve's suggestion above should work for this scenario.
You can extend SPTemplateItemProcessor and override SaveBucketImport.
The Shopify tags are already available in the imported external product object (bucket.Product?.Extern?.Tags), so you can process them after the standard import and create/update the corresponding Sales Category assignments.
For example, the customization point would be:
[PXOverride]
public async Task SaveBucketImport(SPTemplateItemEntityBucket bucket,
IMappedEntity existing,string operation,
CancellationToken cancellationToken, SaveBucketImportDelegate baseMethod)
{
// Read tags from bucket.Product?.Extern.Tags
// Map tags to Acumatica Sales Categories
// Create/update category assignments
await baseMethod(bucket, existing, operation, cancellationToken);
}Hope this helps!
+4@Adcirruserp There's no mapping for it. The connector doesn't import Shopify tags at all, and that applies to the template and matrix item import the same way it applies to plain stock items. Product images are in the same bucket. There's also no Sales Category entity on the Shopify side of the connector, so nothing else is going to bring a category taxonomy across. BigCommerce has that entity, Shopify doesn't.
The connector only runs this road in the other direction. On Shopify Stores (BC201010), Inventory tab, set Sales Category Export to Export as Product Tags and Acumatica pushes each item's sales categories out as tags. Before you turn that on, read this thread on how it treats tags you set by hand in Shopify: https://community.acumatica.com/retail-113/merge-sales-category-export-as-product-tags-in-shopify-18034
The one taxonomy field that does import is the Shopify product Type. It lands as the item class, and you pick which class with the Substitution List for Item Classes on that same Inventory tab. If your tags are really acting as categories, moving them into Type is the supported route.
Otherwise you're assigning sales categories in Acumatica after import. An import scenario keyed on the External SKU cross-reference handles that fine.
+4@Adcirruserp Nothing in configuration, no. For Shopify the item entities only get Export Mapping and Export Filtering tabs on Entities (BC202000), so there's no import mapping row to add. Sales Categories isn't an available mapping target on the item side in either direction either, which is why the export path reaches tags through a store setting rather than through a mapping row.
Code is the only route inside the connector, and it's more tractable than it sounds. SPTemplateItemProcessor is a graph, so a graph extension with a PXOverride on SaveBucketImport behaves normally. The tags are already in the product payload the connector pulled, so you aren't making a second call to Shopify. You read them off the extern object and write the category rows onto the template item yourself.
Decide two things before you write it. Whether an unrecognized tag creates a new sales category or just gets logged. And whether a tag removed in Shopify removes the category, because if it does you're writing a diff rather than an append. Worth knowing this is internal connector API, and 2026 R1 rewrote those types for the GraphQL move, so budget for revisiting it at upgrades.
If what you're really after is a category structure rather than tags specifically, collections carry IDs and tags don't, which makes them a much easier target. There's a thread on that: https://community.acumatica.com/retail-113/sync-acumatica-item-sales-categories-to-shopify-collections-23141
Steve's suggestion above should work for this scenario.
You can extend SPTemplateItemProcessor and override SaveBucketImport.
The Shopify tags are already available in the imported external product object (bucket.Product?.Extern?.Tags), so you can process them after the standard import and create/update the corresponding Sales Category assignments.
For example, the customization point would be:
[PXOverride]
public async Task SaveBucketImport(SPTemplateItemEntityBucket bucket,
IMappedEntity existing,string operation,
CancellationToken cancellationToken, SaveBucketImportDelegate baseMethod)
{
// Read tags from bucket.Product?.Extern.Tags
// Map tags to Acumatica Sales Categories
// Create/update category assignments
await baseMethod(bucket, existing, operation, cancellationToken);
}Hope this helps!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.