Email support@skuforge.app and we’ll reply within one business day.
To help us help you faster, include your .myshopify.com domain, what you expected to happen, and — if a job or scan is involved — the job or scan ID from the URL.
No. Generation only fills variants whose SKU or barcode is empty, and the app refuses to overwrite a non-empty barcode. Bulk edits you make yourself in the editor are the only way to change an existing value.
No, and this matters. SKUForge generates internal Code 128 barcodes. They scan correctly on your own equipment and are ideal for in-store and warehouse use. They are not GS1-issued UPC or EAN identifiers. If you sell on Amazon, or through most retail distributors, you need GS1-issued numbers — buy them from GS1 and enter them yourself. Any app that implies otherwise is misleading you.
Within your store, yes. Every catalog-writing job takes an exclusive per-store lock, re-checks each proposed SKU against live Shopify data immediately before writing, and runs a verification scan after finishing. If anything slipped, the job reports completed with findings rather than claiming success.
Malformed detection is measured against your default SKU rule. If you have not created a rule yet, a generic pattern is used, which may flag SKUs that are fine for your business. Create a rule that matches how your SKUs actually look, then re-scan.
Your access token and session are deleted immediately, and running jobs are cancelled. Shopify then sends an erasure request 48 hours later, at which point every record for your store is permanently deleted. See the privacy policy for the full list.
Uninstall the app from your Shopify admin, or downgrade to Free from the app’s Billing page. Shopify handles the proration.
If SKUForge wrote something to your catalog that you did not expect, tell us immediately at support@skuforge.app with the job ID. Every job records exactly which variants it touched and what it wrote, so we can tell you precisely what changed.