Shop workspace

Shop onboarding · Travel trailers & fifth wheels

Your first history import

Start with two or three closed jobs. Turn each work-order line or inspection finding into a dated entry that a dealer and a buyer can find by trailer VIN.

Before preparing real records, read the contributor terms and privacy notice. Need help mapping a column? Contact the pilot team; do not email completed customer exports.

Prepare the file

  1. Request contributor access. Sign in at the shop workspace and enter your shop’s public name. RigStory reviews the business before it can publish. You can prepare the CSV while you wait.
  2. Start from records your shop issued. Include only completed repairs and issued inspections your shop has permission to share with future buyers. Omit customer names, contact details, addresses, prices, payment details and internal notes. Keep the originals at the shop.
  3. Fill in the template. Keep all ten column headers. Use plain text for VINs and document IDs so leading zeros survive. Export as comma-separated UTF-8 CSV. A file can contain up to 100 rows of history and be up to 512 KiB.

What goes in each column

trailer_vin
17-character VIN from the trailer label, a photo of that label, or a shop intake record that documents the label. Never use the tow vehicle’s VIN.
document_vin
VIN independently recorded on the original work order or issued inspection. Copying one exported VIN into both columns does not verify a match. Leave the job out if you cannot verify both sources.
rv_type
Use travel_trailer or fifth_wheel.
event_date
The date the repair was completed or the inspection was issued, in YYYY-MM-DD format.
event_type
Use repair or inspection. Do not import estimates, scheduled work or draft findings.
system
Name the area or component, such as Roof and seams or Axles and brakes.
summary
Describe the documented work or finding in plain language. A recommendation alone does not establish that a repair occurred.
scope
Required for inspections: what was inspected and what could not be checked. Optional for repairs.
document_reference
A stable, public-safe reference your shop can trace to its document, such as WO-4821. Buyers can see this value.
line_id
A stable line or finding ID within that document. Use 1 for a single item. Keep the same ID on every retry.

Review, publish and check one VIN

  1. Open the CSV importer in your approved shop workspace. Preview the file and compare the rows with the original documents. Nothing is published at this step.
  2. Review the rows marked ready. Fix errors in your file and preview again, or select just the rows you have verified. Confirm you are authorized to publish those rows.
  3. After publishing, open one of the VIN reports and check the service date, source and finding as a buyer would see them. If the import is interrupted, preview the same file again with the same document references and line IDs. Exact repeats do not add history.

To change an entry already on a report, open the VIN report while signed in as the original contributor and use its correction controls. Changing a document reference to get around a conflict can create a second record for the same work.

Go to shop workspace See an example buyer report