Preparing Dealer Brand App content
Preparing Dealer Brand App content
Preparing Dealer Brand App content
A vehicle on the website is a store product with a VIN, an asking price, and a rooftop. If it has no VIN, or no price, it does not publish. Shoppers never add it to a cart.
This is the dealer-pack page for the features/inventory sidebar slot. It is stock for a rooftop, not a warehouse ERP screen.
| Status | Meaning on the site |
|---|---|
available | Can be shown |
pending | Still a dealer vehicle; your desk copy should say it is spoken for |
in_transit | Not on the lot yet |
sold | Removed from the public advertisement after delivery, or after a full import that no longer lists that VIN |
Staff who are admins of a rooftop open /dealer/inventory/import. Paste a JSON array of vehicles, type that rooftop's entity id, and use Dry run first. Dry run counts what would be created or updated and does not write. Apply writes. The screen always sends an incremental import: it adds and updates the VINs in the file and leaves other units alone.
Each row needs a 17-character VIN and an asking price. Rows that are only a title are filled from NHTSA vPIC when the title does not contradict the VIN. A row that disagrees with the VIN decode is skipped, and the report says why.
The same screen lists three names as planned and not connected: Carfax history reports, vAuto pricing, and CDK DMS sync. Do not promise those to a customer.
Delivery is a staff action, not a button on the public page. A rooftop member calls POST /api/dealer/vehicles/<product id>/deliver with the buyer's user id. That sets the unit to sold, zeroes the public stock, and can place the car in the buyer's garage. If you also pass an opportunity id, that lead moves to sold.
A full import (mode: full on the API, not on the current screen) marks VINs that are no longer in the file as sold. Use that only when the file is the whole rooftop, not a partial list.
No. Apply is the button that writes.
Not unless they are an admin of that rooftop, or a platform admin. A member can deliver a sold unit. Import is the stricter role.
The report lists the VIN. Usual causes: the VIN is not 17 characters, there is no asking price, or the title does not match the decode.
A vehicle on the website is a store product with a VIN, an asking price, and a rooftop. If it has no VIN, or no price, it does not publish. Shoppers never add it to a cart.
This is the dealer-pack page for the features/inventory sidebar slot. It is stock for a rooftop, not a warehouse ERP screen.
| Status | Meaning on the site |
|---|---|
available | Can be shown |
pending | Still a dealer vehicle; your desk copy should say it is spoken for |
in_transit | Not on the lot yet |
sold | Removed from the public advertisement after delivery, or after a full import that no longer lists that VIN |
Staff who are admins of a rooftop open /dealer/inventory/import. Paste a JSON array of vehicles, type that rooftop's entity id, and use Dry run first. Dry run counts what would be created or updated and does not write. Apply writes. The screen always sends an incremental import: it adds and updates the VINs in the file and leaves other units alone.
Each row needs a 17-character VIN and an asking price. Rows that are only a title are filled from NHTSA vPIC when the title does not contradict the VIN. A row that disagrees with the VIN decode is skipped, and the report says why.
The same screen lists three names as planned and not connected: Carfax history reports, vAuto pricing, and CDK DMS sync. Do not promise those to a customer.
Delivery is a staff action, not a button on the public page. A rooftop member calls POST /api/dealer/vehicles/<product id>/deliver with the buyer's user id. That sets the unit to sold, zeroes the public stock, and can place the car in the buyer's garage. If you also pass an opportunity id, that lead moves to sold.
A full import (mode: full on the API, not on the current screen) marks VINs that are no longer in the file as sold. Use that only when the file is the whole rooftop, not a partial list.
No. Apply is the button that writes.
Not unless they are an admin of that rooftop, or a platform admin. A member can deliver a sold unit. Import is the stricter role.
The report lists the VIN. Usual causes: the VIN is not 17 characters, there is no asking price, or the title does not match the decode.
A vehicle on the website is a store product with a VIN, an asking price, and a rooftop. If it has no VIN, or no price, it does not publish. Shoppers never add it to a cart.
This is the dealer-pack page for the features/inventory sidebar slot. It is stock for a rooftop, not a warehouse ERP screen.
| Status | Meaning on the site |
|---|---|
available | Can be shown |
pending | Still a dealer vehicle; your desk copy should say it is spoken for |
in_transit | Not on the lot yet |
sold | Removed from the public advertisement after delivery, or after a full import that no longer lists that VIN |
Staff who are admins of a rooftop open /dealer/inventory/import. Paste a JSON array of vehicles, type that rooftop's entity id, and use Dry run first. Dry run counts what would be created or updated and does not write. Apply writes. The screen always sends an incremental import: it adds and updates the VINs in the file and leaves other units alone.
Each row needs a 17-character VIN and an asking price. Rows that are only a title are filled from NHTSA vPIC when the title does not contradict the VIN. A row that disagrees with the VIN decode is skipped, and the report says why.
The same screen lists three names as planned and not connected: Carfax history reports, vAuto pricing, and CDK DMS sync. Do not promise those to a customer.
Delivery is a staff action, not a button on the public page. A rooftop member calls POST /api/dealer/vehicles/<product id>/deliver with the buyer's user id. That sets the unit to sold, zeroes the public stock, and can place the car in the buyer's garage. If you also pass an opportunity id, that lead moves to sold.
A full import (mode: full on the API, not on the current screen) marks VINs that are no longer in the file as sold. Use that only when the file is the whole rooftop, not a partial list.
No. Apply is the button that writes.
Not unless they are an admin of that rooftop, or a platform admin. A member can deliver a sold unit. Import is the stricter role.
The report lists the VIN. Usual causes: the VIN is not 17 characters, there is no asking price, or the title does not match the decode.
