Loading...
Loading...
Add a vehicle to the dropdown list that doesn't have any SKUs in the system yet.
Share suggestions, report issues, or leave comments.
You must change your password before continuing.
Manage secondary inventory locations (vans, satellite shops, etc.).
Non-SKU equipment & miscellaneous inventory tied to this location (tools, machines, supplies). Not part of key stock.
Loadingโฆ
Upload a CSV with SKU and Cost columns to set base-level key costs. These will be used as the starting average cost and will naturally blend with real PO data as you receive orders.
Example: LEX-23, 42.50This will NOT change inventory quantities. It records purchase history and updates average cost calculations for the financial dashboard.
Applied to the order total only. SKU unit costs and average cost calculations are not affected.
This will NOT change inventory quantities. It records sales history for the financial dashboard and revenue tracking.
Build a transponder key from a shell and a chip. The chosen quantity of shells and chips is removed from shop inventory, that many of the target SKU is added, and the target's PO cost is set from the combined cost of one shell + one chip.
Report inventory that is damaged, lost, or stolen. Each item is deducted from stock and recorded as a loss valued at its average cost. The reason and date are saved and shown in the Financial Dashboard.
Applied to the order total only. SKU unit costs and average cost calculations are not affected.
Discounts here lower the order total only. Per-SKU unit costs and average cost calculations stay based on true list price, so your cost-per-key numbers stay accurate.
Enter the quantity to return for each line. Returned items are removed from inventory. The order/receive/return history is kept for your records.
Add a line per SKU. Search the SKU, then enter a quantity โ positive to add, negative to remove.
Select group, type, or both. Leave prices empty to skip.
Drag & drop CSV or
Upload CSV to mass-update fields. Blank cells skipped. Quantity never changed.
Enter past purchase orders and sales for financial tracking. These do not affect current inventory quantities but do count toward average costs, revenue, and profit calculations.
Track SKU usage and restocks over a date range.
Monthly audits check a random sample (~10%) of SKUs. Quarterly audits cover the entire inventory. Due on the 1st of each month/quarter.
Map Service Fusion products to your SKUs and assign techs to sublocations. (Setup โ item & tech mapping.)
Pull shop sales from Square and stage them as daily sales. (Setup โ catalog cache & sync.)
Type DELETE ALL to confirm.
Upload a Service Fusion Product Catalog export (.xlsx). Inactive items are ignored. Clean 1:1 matches auto-map; duplicates and name conflicts are held for your review.
Assign each Service Fusion tech to the van (sublocation) their jobs deduct from. Use Shop for the shop-stock tech. Leave None for non-automotive techs โ their jobs only flag for review if they contain a tracked key.
Tech IDs and names come from Service Fusion job data. Add them here as you encounter them, then set each one's sublocation.
Enter your Service Fusion API credentials (used to pull jobs). Stored locally.
Jobs that couldn't be auto-staged (unmapped tech, multi-key ambiguity, etc.). Fix the underlying mapping, then re-run the sync to pick them up.
Enter your Square Production access token, then pick your active location.
Square lines that didn't map to a tracked SKU (not in app, no catalog SKU, or custom amount). As you add these to Square/your app, they'll start matching.