Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The rules apply to Apparel & Footwear through APIs, File Exchange, and third-party listing tools. They do not impose one universal size table on every eBay category.
- From June 2026, high-confidence legacy values may be normalized automatically. From August, new and existing listings with non-standard, missing, or incomplete sizes may be hidden, held, or blocked.
- Inventory API 1.18.8 added a new size-standardization blocking error on August 24, 2026. Record HTTP success, warnings, holds, and blocking errors separately.
- Do not hard-code Small, S, See description, custom waist measurements, or different national sizing systems as interchangeable. Use the target marketplace, category, and official item-aspect values.
- Export affected listings, preserve original values, fix a small batch, and verify storefront visibility. Stop the batch and retain response evidence if mappings are uncertain or many listings go on hold.
What Changed: Unchanged Listing Requests Now Leave Fashion Products on Hold
eBay is standardizing Apparel & Footwear sizes. Its developer guidance says high-confidence values have been automatically normalized since June 2026—for example, Small to S—while low-confidence or invalid values such as See description and N/A are flagged. From August, new and existing listings with non-standard or missing sizes, or missing condition, may be blocked or held. Inventory API 1.18.8 added a new size-standardization blocking error on August 24.
A typical case is a team updating clothing in bulk with the same CSV or API payload. The task says it was sent, but some SKUs are no longer public or the batch remains in an error queue. The cost is interrupted sales, manual rework, and inconsistent inventory states. Endless resubmission or arbitrarily replacing custom values with S/M/L is the wrong response. First freeze the failed batch and retrieve the current permitted Size aspect for each marketplace and category.
Old Versus New Rules: Automatic Normalization Does Not Fix Every Value
eBay may normalize high-confidence values automatically, so your system might still say Small while eBay displays S. This is a mismatch between source and platform values that needs a listing read-back and synchronization, not an assumption that someone tampered with the product. Low-confidence, invalid, missing, or incomplete values may not be resolvable automatically and require seller or integrator correction.
The official dates refer to separate phases: June marks the start of automatic normalization, August the enforcement of hiding, holds, or blocking, and August 24 the Inventory API 1.18.8 release documenting the blocking error. They are not one moment and do not imply every marketplace, category, and call switched at the same minute.
Distinguish Warnings, Holds, and API Blocking Errors
Save the HTTP status, API method, error or warning code, message, marketplace, categoryId, SKU, original Size, and condition. If the API rejects a request, correct the payload before resubmitting. If the request succeeds but the listing goes on hold, query listing status and public visibility. If the value was only normalized automatically, read back the platform value and update the internal mapping.
Do not rely only on a batch process's completed status. A successful CSV upload can still contain row-level failures, and HTTP 200 can carry a business warning. Conversely, a network timeout before a response arrives is different from a size-related blocking error that has already been returned.
Build Marketplace and Category Value Lists Before Bulk Changes
Retrieve item aspects for the target marketplace and leaf category. Confirm whether Size is required, its permitted values, variation usage, and condition requirements. Map platform values to ERP, PIM, CSV-template, and third-party-tool fields while preserving original supplier sizes. Children's clothing, shoes, menswear, womenswear, and national sizing systems should not share an unverified replacement table.
Prioritize missing values, See description, N/A, free-text combinations, and sizes recorded only in the title or description. If the physical item cannot be mapped reliably to an allowed value, do not guess the closest size. Pause that SKU, obtain measurements, or confirm the category configuration with eBay or the tool provider.
Small-Batch Corrections and Read-Back Verification
First, export affected SKUs, marketplaces, categories, original sizes, and listing statuses. Second, select 5 to 10 low-risk samples covering different symptoms. Third, update Size and required condition using current allowed values. Fourth, read back API or Seller Hub status. Fifth, check the public storefront while signed out to confirm visibility, selectable variations, correct prices, and stock. Sixth, expand in batches while recording success, warning, hold, and failure counts for each batch.
Keep corrections reversible by saving the original payload, mapping version, action time, and response. If an old sync job would overwrite values normalized by eBay, pause that write-back first; otherwise you may create a loop between Small and S.
Update Third-Party Tools and Inventory API Integrations Together
When publishing through File Exchange, an ERP, or a listing tool, confirm that it has refreshed eBay's aspect metadata and error handling. Inventory API clients must record the new blocking error instead of swallowing unknown errors or marking a whole page of SKUs as network failures. Multichannel systems should keep eBay's standardized values within the eBay mapping layer rather than overwriting original sizes needed by other platforms.
Regression checks should cover standard values, automatically normalizable values, missing values, invalid free text, multiple variations, different marketplaces, and unknown new errors. A failed item must not move that SKU into a success state or block other SKUs that can be processed independently.
Stop Conditions, Common Mistakes, and Network Boundaries
Stop a batch if the marketplace or category is uncertain, the same value behaves differently across categories, listings remain invisible after correction, old sync jobs repeatedly overwrite new values, error codes are not captured, or many existing listings go on hold together. Retain original responses, batch IDs, SKUs, and the time window, then ask the tool provider or eBay support to investigate.
Common mistakes include assuming automatic standardization fixes everything, treating a size in the description as structured Size, interpreting an API release date as the exact start for every seller, and mistaking a business block for a proxy connection failure. Use the proxy connection troubleshooting checklist only with connection-layer evidence such as DNS, TLS, timeout, or 407 errors. The network exit cannot change eBay's permitted size values.
Rollout Checklist and Follow-Up Checks
Before rollout, confirm the target marketplace and category, saved current aspects, preserved original sizes, manually sampled mappings, separate warning/hold/blocking-error counts, traceable CSV row results, verified read-back and public visibility, protection against sync overwrites, and a clearly assigned owner who can stop the batch.
Check listing visibility, variation selection, stock, and new errors 24 hours after the fix. A week later, reread eBay API Updates, Inventory API Release Notes, and Seller Center. If official allowed values or error meanings change, update the original page and mappings rather than creating near-duplicate pages for the same size-standardization event.
Sources
Frequently Asked Questions
Which eBay products are affected by size standardization?
The current official guidance covers Apparel & Footwear through APIs, File Exchange, and third-party listing tools. Verify actual required fields and allowed values for each marketplace and category.
Why did Small become S?
Since June 2026, eBay has automatically normalized some high-confidence values. Integrators should read back the platform value and update their mapping while preserving the original supplier size.
Why is a listing hidden or on hold?
From August 2026, non-standard, missing, or incomplete sizes and related condition problems may cause hiding, holds, or blocking. Determine the cause from the specific response and listing status.
What changed in Inventory API 1.18.8?
eBay's August 24, 2026 release notes say this version added a new blocking error for Apparel & Footwear size standardization.
Can I replace every custom size with the nearest standard value?
That is not recommended. Allowed values vary by marketplace, category, audience, and product type. Pause a SKU rather than guessing when a reliable mapping is unavailable.
What if the listing is still invisible after correction?
Stop expanding the batch and retain the SKU, marketplace, category, original value, response, batch ID, and time. Check condition, sync overwrites, and listing status, then contact the tool provider or eBay support.