Home / Businesses / SKU Normalize and Duplicate Check
SKU Normalize and Duplicate Check
Normalize a batch of SKUs (case, separators, leading zeros, by the options you choose) and list the codes that collide, split into exact duplicates and different spellings, with a signed record.
Testing
- What it does
- Normalize a batch of SKUs (case, separators, leading zeros, by the options you choose) and list the codes that collide, split into exact duplicates and different spellings, with a signed record.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
sku_normalizeat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
SKU Normalize and Duplicate Check is for agents that clean a product feed, merge two catalogs or prepare an inventory import and must find SKUs that are the same code typed two ways before they create duplicate listings. Normalize a batch of SKUs and find the ones that collide. Send skus (up to 200) and choose: case (upper, lower or keep), separators (hyphen: every run of space . _ / - becomes one hyphen; remove: they are dropped; keep: left as typed) and strip_leading_zeros (true or false). Get back each SKU's normalized form, and the collision groups: SKUs that become the same code, split into exact duplicates (typed identically) and different spellings of one code (AB-001, ab 001, AB001 under the remove option). Use it to clean a product feed or merge two catalogs before import. It is one of the E-commerce department tools LLPRO builds for the work agents do across business software (Shopify, WooCommerce, Bigcommerce, Amazon Seller Central, Etsy). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents that clean a product feed, merge two catalogs or prepare an inventory import and must find SKUs that are the same code typed two ways before they create duplicate listings.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, skus up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not know your catalog's real SKU scheme: 'AB-001' and 'AB001' may be different products to you, so choose the options that match how you treat codes (remove merges more, hyphen merges less, keep with case keep merges only exact duplicates). Stripping zeros can merge codes that differ only by padding, including barcodes (012345678905 and 12345678905), so leave it off for GTINs. Does not check GTIN check digits, spelling, or whether products are the same item. Refuses codes with an @, web address, an SSN or phone-number shape, or a run of more than 14 digits; names with a known domain ending (.com, .net ...) are refused as web addresses. Not advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "sku_normalize", "arguments": {"skus": ["ab-001", "AB 001", "AB001", "ab_0001"]}}}For agents
Tool sku_normalize on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:u7oa6pxj2f3lkstebulm2tpxha): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): tiEsDsPMC2UiYC7+MpD8qGxShPeXXxVsFomm7kAspOk=
For agents that search MCP registries for SKU normalize, duplicate SKU, product feed cleanup tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to LLPRO: SKU cleanup is one step of catalog work. Tell LLPRO the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card