Locations are your shops, and almost everything in WickedFile is filtered or grouped by them. A new shop needs a location before its documents, statements and numbers can be read separately from the rest of the group.

This article covers adding a location, the part of the setup that support handles, how to name locations consistently, and what to do after a new one exists.

The location on a document decides which shop's numbers it lands in, which manager gets asked about it, and which statement it reconciles against.

The last of those has the widest effect. A vendor billing five of your shops sends five statements, and each one reconciles against the documents for that shop alone. A document filed to the wrong location reports as missing on one statement and unexpected on another.

The first two steps are self-serve. The third is not, and the reason is in why you cannot connect an integration yourself.

Support connects the shop management system so repair orders for the new shop start arriving, and maps which shop in that system corresponds to this WickedFile location.

Until that mapping exists, the location works for filing documents, but no repair orders are arriving for it, so parts cannot be traced to jobs. Lines from that shop land as uncategorized spend. This is expected for a new location and it resolves once the connection is live.

Raising the ticket when you create the location rather than later keeps that window short.

Use the name your team says out loud. If everyone calls it Cedar Springs, name it Cedar Springs rather than using the legal entity name.

Keep the pattern consistent across shops. Location names appear in filters, on every document row, in statement groups and in manager requests, and one shop formatted differently from the others is harder to pick out of a list.

Three things to do straight away.

Assign the manager. A store manager assigned to their own shop sees requests for that shop only. See invite a teammate and choose their role.

Check vendor coverage. A vendor that will bill this shop needs its statement coverage to include the new location, or the shop will never show as awaiting a statement from that vendor. See which vendors send you statements.

Map the card, if the shop has its own. Transactions from an unmapped card show a location of Undefined. Matching still works, but that spend cannot be filtered by shop.

This pane also holds per-location billing, which is marked coming soon in the product. Billing questions go to support rather than being self-serve today.

Renaming a location is safe and updates the name everywhere it appears.

Removing one affects history, because past documents and statements belong to it. When a shop closes, contact support rather than deleting the location, so its history stays readable.

The full first-week sequence, including locations, is in setting up your first week.