CoreBack Native core return template + sync guide
This page is for repair shops using CoreBack Native. It gives you a working CSV template, a field-level mapping reference, and a shelf-first import workflow that fits CoreBack's vendor-agnostic return process without requiring a DMS integration.
Who this solves for
Why this CoreBack Native page exists
A normal DMS export rarely includes tracking number, label ID, memo number, and closeout fields in one place. The CoreBack native format does.
In practical terms, the template keeps the invoice export lightweight while CoreBack handles the part the DMS does not: the visible shelf queue, the bag label, the deadline discipline, and the final credit-close step. That is why these pages are intentionally task-specific instead of generic software copy.
ACCEPTED DATE FORMATS
YYYY-MM-DD
Import spec
Field requirements at a glance
part_number · vendor · invoice_number · due_date · core_value
bag_label · description · invoice_date · status · tracking_number · credit_amount · credit_memo · credit_date
A real sample CSV is available from the button above and mirrors this mapping table.
Template mapping
Field-by-field reference for CoreBack Native
| CSV column | CoreBack field | Required | Example | Hint |
|---|---|---|---|---|
| id | _ignore | Optional | demo-1 | Internal CoreBack ID (ignored on import) |
| bag_label | bag_label | Optional | CB-DEMO1-184532 | Unique bag label — used for dedup on re-import |
| part_number | part_number | Required | 18-5432 | — |
| description | description | Optional | Alternator Core 100A | — |
| vendor | vendor | Required | NAPA Auto Parts | — |
| invoice_number | invoice_number | Required | INV-2024-08821 | — |
| invoice_date | invoice_date | Optional | 2024-02-19 | — |
| due_date | due_date | Required | 2024-03-20 | — |
| core_value | core_value | Required | 85.00 | — |
| status | status | Optional | open | — |
| tracking_number | tracking_number | Optional | — | |
| credit_amount | credit_amount | Optional | — | |
| credit_memo | credit_memo | Optional | — | |
| credit_date | credit_date | Optional | — |
Export workflow
From CoreBack Native export to live shelf
- 01Open Sync and export the CoreBack-native CSV when you need a complete ledger snapshot.
- 02Move the file to the destination location, archive folder, or accountant handoff.
- 03Re-import using the CoreBack Native template so bag labels and closeout fields survive the round trip.
- 04Use bag_label as the dedupe anchor so updates do not create duplicate shelf items.
The point is speed with verification. You should be able to drag in a raw export, resolve only the rows CoreBack flags, and get back to the shelf without hand-editing every column. That is why the mapping table is explicit and why the error states below are written like operational fixes, not generic SEO filler.
Worked example
What the first import usually looks like
An owner wants one monthly archive that includes every open, shipped, and credited core across locations.
Each shop has its own spreadsheet and none of them agree on bag IDs or memo references.
The CoreBack-native export becomes the reconciled monthly ledger with consistent fields for finance and operations.
Validation guide
Common import errors and how to fix them fast
The bag_label was deleted or altered before re-import.
Preserve bag_label exactly as exported whenever you want CoreBack to treat the row as an update rather than a new shelf item.
The export happened before the memo and credit were confirmed.
Run a fresh native export after closeout if you need the most current recovery ledger.
Exports keep system-friendly status values rather than marketing labels.
Use the native file for system handoff, not as a polished staff-facing checklist.
Next step
Use the template, then move straight into activation
The best template pages do not stop at documentation. This one intentionally points you into the next concrete action: create a free CoreBack account, land inside onboarding with the CoreBack Native context in the URL, and import a real batch the same session. If the shop is still evaluating workflow fit, the comparison and ROI links below give the next most useful decision paths without sending the visitor into generic awareness content.
FAQ
CoreBack Native import questions we expect from real shops
When should I use CoreBack Native instead of a DMS template?
Use it for round trips, backups, and consolidated reporting — not for pulling fresh invoice activity out of a DMS.
Does it preserve QR label IDs and closeout data?
Yes. That is the main reason this format exists.
Can multiple locations use the same native schema?
Yes. It is the cleanest way to move validated return data between locations without remapping fields each time.