Contact
One inbox, read by a person. There is no ticket system and no chatbot in front of it.
What is most useful to send
- A rule that is wrong. Quote the rule ID shown next to it (something like
GTIN-005) and say what the correct behaviour should be. This is the single most valuable message this project receives — a wrong rule stated confidently is worse than a missing one. - A source link that has rotted. Specifications move and help centres get reorganised. Tell us which tool and which rule, and it gets re-verified against the publisher rather than patched from memory.
- A file a tool got wrong. Describe what was in it and what the tool said — please do not attach the file. Real-world breakage of this kind usually ends up as a permanent regression test.
- A tool that should exist. Say what the task is and what you do today instead. Concrete workflows beat feature names.
- A security issue. Send it to the same address with “security” in the subject line and it goes to the top of the pile.
Please do not send us your data
Every tool here runs inside your browser, so we have no facility for receiving product catalogues, invoices or scans — and no way of processing them better than the page in front of you already does. A description of the problem is more useful than the file, and safer for you. What does and does not leave your browser is set out in the privacy policy.
What to expect
This is a small, independently run project, so replies take a few days rather than a few minutes. Corrections to rules and sources are acted on whether or not a reply goes out first. More about how the tools are built and maintained is on the about page.