“You may have reached the API calls limit” from Cin7 Core to Shopify

Cin7 Core’s own Shopify Integration FAQs carry the question verbatim: "I get an error message saying ‘Failed to create or update the product in Shopify: You may have reached the API calls limit. Please try again in a minute.’ What does this mean?"

The answer Cin7 gives has nothing to do with API limits. It reads: "It looks like there is a problem with some of your products in Shopify, they have default variations with SKUs that are different from the ones in Cin7 Core. In this case, Cin7 Core finds relevant products by name but doesn’t find variations by SKU (they are different in Shopify and Cin7 Core). Instead, Cin7 Core tries to create a default variation with a new SKU. The process is failing because Shopify only allows a single default variation for a product, unlike a product family with multiple variations."

So the visible message is misleading by design of the error handling rather than by intent, and following it will send you to look at rate limitA rate limit is the cap a system puts on how many API requests you may make in a period. Go past it and requests are rejected until the window resets. settings that are not the problem.

A SKUA SKU is the code a business uses to identify one specific sellable item, including its size, colour or pack. It is internal to your business, unlike a UPC or EAN, which identifies the product globally. mismatch on a single-variation product, on a product that already exists in both systems. The sequence is worth holding in your head because it explains why the error looks like a throttle: Cin7 Core matches by name, then tries to match the variation by SKU, fails, decides the variation does not exist, and attempts to create one. Shopify refuses. Cin7 Core reports the refusal with a generic message.

The precondition that makes this common is Cin7 Core’s own rule that SKUs are mandatory. Its documentation states that "products without SKUs will not be accepted in Cin7 Core since SKUs are mandatory in Cin7 Core", and that auto-generating missing SKUs is not supported. So a Shopify catalogue built without disciplined SKUs, which is most of them, meets a system that will not tolerate that.

Align the SKUs. There is no setting for this, and no amount of waiting a minute and retrying will help.

Then consider that it might genuinely be a rate limit, which does exist. The tell is the shape of the failure: a SKU mismatch fails the same products every time, and a real throttle fails different products on different runs and clears on retry. Count the failures across two runs before you conclude anything.

If you are on Cin7 Omni rather than Cin7 Core, this is not your page. Omni documents its own separate set of Shopify error strings, including "Not found", "The variant already exists", "Option is not unique" and "The api_client does not have the required permission(s)", each with its own cause and fix.

Both Cin7 help centres were read on 20 August 2026. Cin7 ships changes continuously and does not publish a release calendar the way Acumatica does, so re-check the current article before you build a runbook on this.