Import Results and Fixing Errors
After you submit a catalog or inventory file, Kennicott Core processes it and gives you a result. This page explains what each status means and what you should do.
Catalog import statuses
We received your import
Your file was uploaded and a job was created. Kennicott Core hasn't started processing yet or is about to start.
What Kennicott Core will do: Begin processing automatically. What you do: Wait. Processing usually starts within a few seconds.
We are processing your import
Kennicott Core is reading your file and validating each row against your configured format.
What Kennicott Core will do: Continue until complete. What you do: Wait. Check again in 15–30 seconds for large catalogs.
Your import is done — nothing to review (AUTO_PROCESSED)
Processing is complete and everything committed cleanly. This is the normal outcome for a valid submission.
What Kennicott Core will do: Nothing further is required from your administrator. If some products are missing a price or availability date, they're still saved — call the enrich endpoint to add the missing fields, then publish (or wait for auto-publish, if your connection has it enabled).
What you do: Nothing, unless a product needs enrichment before it can go live.
Your import needs attention (READY_FOR_REVIEW)
Processing is complete, but at least one row has a real problem — a validation error or a conflicting duplicate — that has to be fixed before that item can be committed.
What Kennicott Core will do: Everything else in the batch that didn't have a problem is still committed automatically. Only the flagged rows are held back.
What you do: Check the portal (or ask your administrator) for a summary of what was flagged:
- Rows with validation errors (see error table below)
- Rows with conflicting duplicate values — fix the source data and resubmit
- Package specification changes that need admin review
Your products are ready to publish
All required fields are present. If your connection has auto-publish enabled, this happens automatically after committing. Otherwise, your administrator (or your own system, via the publish endpoint) can publish these products to Shopify.
What Kennicott Core will do: Publish to Shopify automatically (if auto-publish is on) or when the publish endpoint is called. What you do: Nothing, unless you need to trigger publish yourself.
Your import failed (FAILED)
Processing stopped due to a file-level error. No products were staged.
What Kennicott Core will do: Retain the error information. What you do: Check the error message in the portal or via the status API. Fix the issue and resubmit.
Common causes:
- File could not be read (encoding issue, incomplete upload)
- Required column headers missing
- Presigned upload URL expired before the file was uploaded (create a new job)
Your import is complete (COMPLETED or PARTIAL)
Products have been committed. PARTIAL means some families were committed and some were skipped (usually because they're still missing required fields).
Understanding row-level results
Each row in your file gets a result. Here's what each result means and what to do.
| What you see | Why it happened | What to do |
|---|---|---|
| Ready to publish | All required fields present | Nothing — your admin will publish |
| Staged, needs enrichment | Missing price or availability dates | Add price and dates via enrichment or portal |
| Needs enrichment (missing required fields) | Missing SKU, product name, box type, or sell unit | Fix your source data and resubmit |
| Exact duplicate — deduplicated | Same row appeared twice in the same file | No action needed — safely removed |
| Conflict | Same product code + box type appeared with different values | Check your source data for inconsistencies |
| Package spec changed | An existing variant's box configuration changed | Your admin will review and decide how to handle it |
| Error | Field validation failed (see error table below) | Fix the field and resubmit |
| Skipped | Blank or unsupported row | Review the row; ignore if intentionally blank |
Common field errors
| What you see | Why it happened | What to do |
|---|---|---|
availableFrom must be in YYYY-MM-DD format | Date is in a different format | Use 2026-07-01 format |
status must be 'active' or 'inactive' | Status value is not recognized | Use active or inactive (lowercase) |
vendorId cannot be provided | You included vendorId in the payload | Remove it — Kennicott Core resolves this from your API key |
Raw Shopify metafield key not accepted | You used a Shopify field name like custom.availablefrom | Use Kennicott Core field names like availableFrom |
price must be a decimal number | Price includes a currency symbol or is invalid | Use 42.50 not $42.50 |
deliveryLeadDays must be between 0 and 365 | Lead time value is out of range | Use a whole number between 0 and 365 |
Inventory result codes
When you submit inventory, each item gets one of these results:
| Result | Meaning |
|---|---|
APPLIED | Count accepted. Balance updated. |
NO_CHANGE | Submitted count equals current on-hand. No update needed. |
REJECTED_STALE | Your sourceUpdatedAt is older than the last accepted count for this variant. |
HELD_BY_OVERRIDE | An admin override is active. Count stored for review but not applied. |
REJECTED_NOT_AUTHORITATIVE | Your account is not configured for API inventory updates. |
UNKNOWN_VARIANT | sourceSku not found in your Kennicott Core catalog. Submit the product via catalog API first. |
AMBIGUOUS_VARIANT | sourceSku has multiple variants and vendorVariantCode was not provided. |
How to fix and resubmit
If rows had errors:
- Fix the flagged data in your source file
- Remove rows that were already accepted (or resubmit the full file — Kennicott Core is idempotent and won't create duplicates)
- Upload the corrected file as a new job
- Check the new job's results
Submitting the same data again is safe. Kennicott Core looks up existing variants by your product code and pack size — it updates them rather than creating duplicates.
What to do when something is stuck
| Situation | What to do |
|---|---|
Job has been in PARSING or VALIDATING for more than 5 minutes | Contact your Kennicott Core administrator with the job ID |
You see FAILED but don't have an error message | Contact your Kennicott Core administrator with the job ID |
| Products are staged but not appearing in Shopify after several hours | Contact your Kennicott Core administrator |
Next step
→ API Reference — for technical details on endpoints and fields → Support — how to get help