GTIN and Attribute Cleanup Before Any Media Spend

In the last eleven Gulf catalogues we ran pre-flight on, the median share of revenue-carrying ASINs failing at least one blocking check was 18 percent. Almost none of those failures were exotic. They were identifiers bought from barcode resellers instead of licensed through GS1 Emirates, so Amazon's validation could not tie the 629 prefix to the brand that owns the listing. The ads pointed at those ASINs kept spending. This engagement is that fix, and it is the work we do before we will accept campaign work from anyone. The pre-flight: Twenty-two points, identical on every engagement, sent to you before you sign anything. Identifier validity against the GS1 licence record, 629 for Emirates-licensed brands and 628 for Saudi. Product type resolved through the Product Type Definitions API, then the required and conditionally required attributes that node actually returns, which is rarely what the downloaded flat file suggests. Browse node and item_type_keyword, because between them they decide whether a listing is eligible for the refinements shoppers filter with. Variation family integrity, including children orphaned by a parent edit made two years ago. Buy box ownership across a rolling 30 days. Search suppression and the reason string behind it. For gaming hardware: the lithium-ion declaration and UN38.3 documentation, age rating fields, and the warranty attribute UAE buyers filter on and most catalogues leave empty. How the fixes are applied: Inside your Seller Central or Vendor Central, under your users, with our access removed on the last day. Above roughly 200 SKUs we work through the Listings Items API with PATCH operations rather than flat files: a flat file that fails halfway leaves you reading an error report to work out what changed, while a PATCH answers per attribute. Where a brand holds no in-region GS1 licence we prepare and file the GTIN exemption, brand registry evidence included. We will not list a product against a resold barcode to get around that step, whoever asks. Arabic and English fields: Amazon.ae carries both. Arabic strings pasted out of Word arrive with directional control characters that survive the upload and break title truncation in search results, and you see it on mobile first. We specify the copy, define the field-level rules and QA the rendering. Producing Arabic marketing copy at volume belongs to your translator or to a separate scope; we are not going to pretend that is a catalogue task. Not included: Photography, A+ modules, Brand Store design. New product introduction. Any catalogue that is not Amazon: noon, Namshi and Talabat use different taxonomies and different identifier rules, and a shop that tells you one cleanup covers all of them has only ever worked in the first. Vendor Central chargeback disputes, which are a finance argument rather than a data one. Who should not buy this: A team that wants an error report and will handle remediation itself. That is a smaller job and we are the wrong price for it. A distributor listing a brand it holds no authorisation for. Anyone who needs this finished inside a week: GS1 licensing and exemption reviews run on their own clock, usually five to fifteen working days, and we do not control it. What you hold at the end: The same 22 points re-run with a before and after column, every feed and PATCH payload we submitted, and a one-page launch check your team runs on each new SKU so this does not become an annual purchase.