Repair a defined ONIX rejection without replacing your metadata system.
Catalogenza turns publisher-authorized ONIX XML and exact rejection evidence into a validated repair package. Your team keeps control of recipient submission.
Catalogenza ONIX Repair Batch
- Up to 10 supported ONIX product records
- Five-business-day target after complete accepted intake
- One correction for a Catalogenza-caused defect
- Digital delivery only; no shipping charge
Corrected ONIX 3.1 XML
Output is checked against Catalogenza's current local official reference schema.
Error-closure report
Each supplied rejection is shown as resolved, unchanged, or blocked by a missing publisher fact.
Provenance and unresolved facts
Authorized changes are traceable. Missing commercial facts are never invented.
Designed for a narrow, current problem
A suitable pilot customer
- Is a U.S. independent publisher or press
- Controls and may provide the source metadata
- Has a current recipient rejection or defined ONIX transition defect
- Can provide supported ONIX XML and exact rejection evidence
- Can certify all rights, price, territory, accessibility, and product facts
Catalogenza will refuse
- Recipient account credentials or submission on the customer's behalf
- Arbitrary spreadsheets during the pilot
- Metadata enrichment, copywriting, or invented facts
- Legal, rights, tax, territory, or accessibility determinations
- Unsupported formats, profiles, or more than 10 records
How the pilot works
1. Qualify
Catalogenza confirms the publisher, trigger, source format, authority, record count, and requested result asynchronously.
2. Accept scope and pay
After qualification, the customer receives the current scope, policies, price, and secure payment instructions. No live checkout is active today.
3. Transfer files securely
The customer uses a designated encrypted file request. Files are not accepted through ordinary email attachments.
4. Repair and validate
Catalogenza performs documented repairs, validates the output, and records every authorized change and unresolved fact.
5. Receive and submit
The customer receives the repair package securely and submits it through its own authorized recipient account.
What validation does—and does not—mean
Schema validation confirms conformance to the ONIX XML structure and code constraints checked by the validator. Catalogenza does not guarantee acceptance by any retailer, distributor, data recipient, or other third party.
Catalogenza does not provide legal, accounting, tax, rights, accessibility, regulatory, or publishing-strategy advice. The publisher remains responsible for the truth, authority, and commercial meaning of supplied metadata.
Built around minimal access
No portal credentials
Catalogenza does not request recipient usernames, passwords, tokens, cookies, or account access.
Separate secure transfer
Source files and deliveries use designated secure links. Customer files are not sent through ordinary email.
Hosted card processing
When live checkout opens, card details will be handled by the hosted payment processor. Catalogenza will not store full card data.
Email Catalogenza
Support is asynchronous by email. Catalogenza does not offer phone, video, or in-person service.
contact@catalogenza.com
support@catalogenza.com
billing@catalogenza.com