Support

Use the beta access form on the public FretTrack site. After applying, watch your email for confirmation and approval messages. If you do not see the email, check spam or junk mail.

Go to app.frettrack-app.com and sign in with the email address approved for beta access.

Confirm your beta access is approved, check whether your email is verified, try a hard refresh, and make sure browser privacy settings are not blocking the sign-in flow. If it still fails, email support with your browser, device, and account email.

FretTrack uses shop roles to limit access. Owners and admins manage shop operations and settings, techs perform repair workflow tasks, and viewers are read-only. Platform operator tools are separate and should not appear for normal shop users.

Owners and admins can manage most shop data. Techs can work on jobs, customers, photos, scheduling, and inventory where allowed. Viewers can inspect records but should not create, edit, delete, receive, upload, or manage settings.

Open FretTrack, choose New Job, enter or select the customer, complete the instrument and repair intake details, then save the job. Use realistic shop data during beta, but avoid private test data unless your shop is prepared to manage it.

Use the Customers area or the customer section during New Job intake. Customer contact fields, email/SMS preferences, and address details should stay attached to the selected customer record.

Open a job and use the work log or history area to record repair notes, updates, and technician activity. Work logs should persist with the job history.

Open the job photos area, upload the relevant image, and wait for the saved preview to appear. Saved photos should reopen from durable links, not temporary local previews.

Use the Damage Map views to document scratches, dents, finish damage, fret wear, serial-number photos, and other intake conditions. Customer-facing reports should show only appropriate repair documentation.

Use the Inventory area to create parts with names, stock quantities, pricing, location, reorder or desired stock values, vendor details, SKU, and barcode identity where available.

Create a purchase order for a vendor, add line items, then receive full or partial quantities when the items arrive. Receiving should update stock, receipt history, purchase order status, and inventory movement records.

When shipping is added to cost, FretTrack can allocate shipping across received items so landed unit cost reflects both item cost and shipping allocation.

Open Reports from the app navigation. Available metrics depend on your shop plan or beta/trial entitlement and the data currently entered in FretTrack.

Advanced Reporting is a Pro-level feature. If it is locked, your shop may not currently have a Pro plan, Pro trial, or operator-granted entitlement.

Download the recommended workbook from /downloads/frettrack-beta-tester-workbook.xlsx. The CSV fallback is available at /downloads/frettrack-beta-tester-checklist.csv.

Use a current desktop browser when possible. FretTrack also includes legacy WebKit compatibility work for older iPad browsers, but very old or unsupported devices may have security, performance, or browser feature limits.

Billing and paid plan management are being prepared for the paid beta period. If billing is available to your shop, use the Billing or Plan area inside FretTrack. If you have questions, contact support.

Refresh the page, sign out and back in, or clear site data for FretTrack if needed. If a deploy just happened, a hard refresh may be needed on some browsers.

Use the in-app Report Issue button first when available. For public-site, login, or access problems, email support@frettrack-app.com.

Include what happened, what you expected, the page or workflow, your shop role, browser/device, account email, steps to reproduce, whether it happens after refresh, and screenshots or video when useful.

Email support@frettrack-app.com. If you are an invited beta tester, also use the beta feedback channel provided with your invite.