Jumia WhatsApp Importer
LIVE Stage 24.1: guided product creation with direct Jumia API publishing and reliable QC edit refresh. QC-passed products can now be submitted to Jumia without manually uploading XLSX files.
Resume saved batch
Upload WhatsApp export
First test with samples/sample-whatsapp-export.zip. After that, use your real supplier WhatsApp export.
ZIP inspection
Choose the WhatsApp day
Your ZIP was read successfully. Choose the one calendar day you want to process.
Show ZIP summary
Detect products
Show raw selected-day messages
PRODUCT DETECTION
Show ignored-message reasons
EDITABLE JUMIA LISTINGS
Accuracy rule: generated fields are editable. Brand becomes Generic when no brand is stated. Weight is deliberately conservative. Color is taken from supplier text when stated; otherwise the browser samples the matched product image and suggests a common color name for you to verify.
Category rule: the generated category is still a suggestion. Stage 5 now binds the batch to the exact columns of the current category template you upload; it never invents category IDs.
Match each product to Jumia
Taxonomy-aware matching: the app first identifies the likely Jumia department (for example Home & Office for kitchen tools), then ranks the most relevant leaf categories. If the right option is not in the suggestions, use the built-in search across all synced Jumia categories. Your corrections are remembered.
Your saved official templates remain available as a fallback/reference only. Stage 17 does not require you to download Fashion, Home & Office, Electronics or other templates manually.
Saved official template library
Optional fallback only: Stage 17 no longer requires manual templates. Keep any official Jumia templates you already saved here for comparison or fallback testing.
For mixed products, choose the matching saved template before binding that category group. Example: Home & Office for mugs, Fashion for clothing. Templates remain Jumia's original XLSX files.
Live Jumia API Schema
Open only when needed: this dashboard reads Jumia's current category tree, leaf categories, attribute sets, mandatory fields, dropdown options and validation rules directly from the Vendor API. Your Client ID and Refresh Token stay on Railway.
You normally only need to sync after Jumia changes categories/attributes or when you want to refresh the cached schema.
Saved-template mixed batch mode
Mixed batch mode: the app compares each product against every saved official Jumia template, assigns the strongest matching template/category, and keeps each product attached to that template through image hosting, pricing, validation and export.
Example: mugs can go to Home & Office while dresses go to Fashion in the same WhatsApp batch. At the end you get separate Jumia XLSX workbooks plus one Jumia_Ready_Uploads ZIP.
Manual single-template fallback
Use this only for a single-category/section batch. Stage 14 above is recommended for mixed categories. For manual use, in Jumia Vendor Center go to Products → Manage Products → Import / Export → Product → Download template, choose the category for these listings, then upload that downloaded .xlsx here. The app reads the workbook locally and does not replace Jumia's template structure.
For this build, use samples/REAL_JUMIA_TEMPLATE_FROM_VENDOR_CENTER.xlsx — the real workbook you supplied from Vendor Center.
Exact workbook structure detected
| Column | Exact header | Mapped app field | Mandatory? |
|---|
Jumia template validation report
Jumia product fields
What changed after reading your real template: mandatory fields are detected from the red borders in the workbook itself. The app also reads the full Brands, Categories and Options sheets instead of guessing values.
Stage 8 below now connects the Arizona254 pricing calculator and can fill Price_KES automatically. MainImage is handled by Stage 7.
Review and host product images
What this stage does: the browser reads the exact matched WhatsApp image, normalizes it to a 1200 × 1200 JPEG without cropping, and the Python backend uploads it to your own public Supabase Storage bucket. The resulting HTTPS URL is inserted directly into MainImage and Image2–Image8.
Important image-quality rule: technical resizing does not magically remove a bad background or restore missing detail. Jumia requires a pure-white main-image background, the full product visible, no text/watermarks, and 500–3000 px dimensions. Stage 7 checks dimensions and public reachability, but you still visually approve the image.
Secret safety: the Supabase secret never enters this web page. In live mode, the Supabase secret is stored only as a protected server environment variable and never enters this web page.
jumia-product-images in Supabase Storage and mark the bucket Public. Then use RUN_WITH_STORAGE.bat instead of RUN_ME.bat. Full steps are in SUPABASE_SETUP.txt.Matched product images
Price with live Jumia-style autosuggest
Same calculator rules: fixed KSh 100 fare, default KSh 20 packaging, 35% net-margin target plus KSh 400 minimum net profit, category commission, and Drop-shipping/Jumia Express logistics fees. Start typing in Product Type to search the full mapped pricing list; the confirmed live Jumia category is used as the strongest hint.
Automatic category per product
Every product is matched independently against the exact Categories sheet from the uploaded Jumia workbook. Strong matches are selected automatically; uncertain ones stay marked for review.
Final QC
Each product is checked before it can be published. Category, required attributes, hosted images, Seller SKU, stock and pricing must all pass.
Publish directly to Jumia
Direct Jumia API publishing: this sends QC-passed products to Jumia using the official product-creation feed. Start with one real product, wait for Jumia's feed result, then publish the remaining products.
The app checks Seller SKU duplicates before submission. A product is synced to Arizona254 only after Jumia returns a successful product result.
Live deployment status
Production mode uses HTTPS hosting, backend-only Supabase secrets, password protection, and cloud import history.
Persistent import history + duplicate protection
A successful final XLSX export is recorded in persistent history. In live mode this history is stored in Supabase, so duplicate protection follows you across devices.
Operations Center
One control room for both shops: accepted, processing, rejected, auto-repairing and products that genuinely need you are tracked here from the persistent server ledger.