Tekmetric core return template + sync guide
This page is for repair shops using Tekmetric. 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 Tekmetric page exists
Tekmetric gives you invoice history, but it does not give you a single return-shelf workflow for bagging, due dates, QR labels, and credit closeout.
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 · MM/DD/YYYY · MM/D/YYYY
Import spec
Field requirements at a glance
RO Number · RO Date · Part Number · Vendor · Core Charge
Part Description · Core Due Date · Core Status · Tracking Number · Notes
A real sample CSV is available from the button above and mirrors this mapping table.
Template mapping
Field-by-field reference for Tekmetric
| CSV column | CoreBack field | Required | Example | Hint |
|---|---|---|---|---|
| RO Number | invoice_number | Required | RO-10042 | Repair Order number used as invoice reference |
| RO Date | invoice_date | Required | 2024-03-15 | Date the RO was created (YYYY-MM-DD or MM/DD/YYYY) |
| Part Number | part_number | Required | 18-5432 | Manufacturer or vendor part number |
| Part Description | description | Optional | Alternator 100A | Part name / description text |
| Vendor | vendor | Required | NAPA Auto Parts | Parts supplier name as shown in Tekmetric |
| Core Charge | core_value | Required | 85.00 | Dollar amount of the core charge on this line |
| Core Due Date | due_date | Optional | 2024-04-14 | Return deadline (if not present, calculated from RO Date + 30d) |
| Core Status | status | Optional | open | open / returned / credit_confirmed (CoreBack adds this on export) |
| Tracking Number | tracking_number | Optional | Carrier tracking number if already shipped | |
| Notes | notes | Optional | Free-text notes |
Export workflow
From Tekmetric export to live shelf
- 01Open Reports in Tekmetric and filter the date range you want to clean up.
- 02Choose the Parts or Parts & Labor export that includes invoice date, part number, vendor, and core value.
- 03Download the CSV exactly as exported — do not waste time reformatting columns first.
- 04Open CoreBack Sync, choose Tekmetric, and drag in the file. CoreBack applies the matching template automatically.
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
A parts manager exports the last 30 days of Tekmetric data after realizing alternator and starter cores are piling up on the shelf.
They have invoice data, but no single view showing which vendor deadlines hit this week or which bags still need labels.
The Tekmetric template maps the rows, CoreBack calculates missing due dates, prints QR bag labels, and creates one prioritized shelf list for the week.
Validation guide
Common import errors and how to fix them fast
The export omits a dedicated due-date column, so CoreBack defaults to invoice date plus your return-window rule.
Set or confirm the vendor rule during import, then bulk-update due dates from the shelf if you need a tighter window.
The Tekmetric report included all parts rather than only core-bearing lines.
Filter the export for rows with a core charge greater than zero or let CoreBack ignore zero-value rows during validation.
The same historical export was imported twice without a stable bag label on older rows.
Use invoice number + part number as the dedupe key for the first pass, then export the CoreBack-native file for round trips.
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 Tekmetric 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
Tekmetric import questions we expect from real shops
Do I need a Tekmetric API integration?
No. This workflow is intentionally CSV-first so a service writer or parts lead can start without IT work or DMS credentials beyond normal reporting access.
Can I keep using Tekmetric for invoicing?
Yes. Tekmetric stays the system of record for invoicing; CoreBack becomes the return-shelf ledger layered on top of that export.
What happens if Tekmetric changes a column name?
The mapping validator shows the mismatch immediately and lets you save an updated template instead of breaking the whole workflow.