Guide · Angaba
Get started with Angaba in five short videos
Each step is under a minute and shows the real app inside a Shopify admin. Angaba extracts, you approve; nothing reaches a live product without your click.
Scan your catalog
The dashboard runs 14 deterministic checks per product against the GPSR disclosure rules and sorts your catalog into Ready, Pending and Missing.
- Missing means the product has no safety disclosure at all. Pending has one with gaps. Ready passes every check.
- Filter to a group, then open any product to see which check fails and why.
- The product page lets you fill the disclosure by hand when you already have the data.
TipOn a password-protected store the theme card cannot verify how your storefront renders disclosures. It turns green once the store is public.
Upload a supplier document
Have a declaration of conformity, a safety data sheet or a manual? Pick the target product, attach the PDF, and Angaba extracts the disclosure data in the background.
- Single product, or bulk mode that matches products by SKU and barcode found in the documents.
- PDF only, 25 MB per job. Documents for a different product are flagged, not applied.
- Extraction takes about half a minute. Reload the list; nothing is written to your product yet.
TipExtraction needs the AI plan. Each document costs one credit; flagged jobs (irrelevant or unreadable documents) cost nothing.
Refuse before wrong
One probabilistic step, quarantined between deterministic checks and a human. Anything below the confidence threshold, without a provenance quote, or failing a format rule is flagged for you rather than guessed.
Review every field against the source
The review page shows the extracted fields on the left and the source document on the right. Every value carries a provenance chip: which page of which document it came from.
- Click a chip and the viewer jumps to that page, so you verify against the document, not against the AI.
- Green chips are extracted with confidence. Yellow says Check this: low confidence or a failed validation.
- The EU Responsible Person is only filled when the documents name one. Angaba never invents it.
Approve and write to the product
Approving is the one moment anything is written. Angaba writes to Shopify's native disclosure field, so Horizon and Dawn themes render it on the product page with no theme work.
- A refused write tells you exactly why: non-EU manufacturer without an EU Responsible Person, missing contact, invalid GTIN.
- Every write gets a gapless ANG id in the append-only audit log, with the source document.
- After approval the job is closed. Re-run the scan and the product moves to Ready.
Import a whole catalog from CSV
Already have the data in a spreadsheet? Download the template, fill one row per product handle, validate, then write. Rows are checked with the same rules as manual entry.
- The template has 15 columns: manufacturer, EU Responsible Person, CE, warnings, identifiers, jurisdictions.
- Rows with errors are listed with line numbers and skipped. They are never partially applied.
- Each written row lands in the audit log with source csv-import.
You are set up when…
Common questions
Is this legal advice?
No. Angaba is a data tool. It structures what your supplier documents say and writes it where Shopify expects it. Compliance obligations remain with you as the merchant.
What if the AI gets a field wrong?
That is what the review page is for. Each field shows its source page; fields below the confidence threshold are marked Check this. Nothing is written until you approve, and every write can be traced in the audit log.
Does it work with my theme?
Horizon and Dawn-family themes render Shopify's native disclosure field automatically. For other themes Angaba ships a Product disclosures block that hides itself when the native section is present.