0052·HS code does not match the provided sale type
Product classificationCommon
What this means
FBR cross-checks product classification against tax treatment. A code belonging to a category that cannot be sold under, say, a Third Schedule or zero-rated sale type will be rejected even though the code exists and the sale type exists.
Why it happens
- The item was classified under a sale type for commercial reasons rather than by its actual tax status.
- A generic or placeholder HS code was applied across a whole catalogue instead of a per-item code.
- The code is right but the sale type was inherited from a template or from another item.
- Goods and services were mixed — service sale types accept a distinct set of codes.
How to fix it
- 1Verify the code against FBR's item code reference and confirm what it actually describes.
- 2Set the sale type from the item's real tax treatment, not from what is convenient.
- 3Where a supplier registered an item under a particular classification, follow theirs — the chain must agree.
- 4Assign HS codes per item. A shared placeholder code will fail across your entire catalogue at once.
How Ordyoo handles this
HS codes are stored per item and validated against FBR's cached reference list when assigned, not at submission. Sale type is inherited from the supplier's registration by default so classification stays consistent along the distribution chain.
Scenarios where this appears
Sandbox scenarios that commonly produce 0052.
Related errors
Stop debugging FBR payloads by hand
Ordyoo builds and submits compliant invoices so most of these rejections never reach you. Start free.
