A Franchise Change of Ownership (FCO) is used to move location data from one site to another. This allows locations to be sold to different entities without interrupting daily operations. This article outlines what information is copied, created, or changed during this process. Visit our other articles for instructions on how to request a Franchise Change of Ownership.
Data copied from the old location
Location data copied from the old location
Location Details. The only change will be the Franchise Entity to match the destination site.
Transfer To locations. Transfers can occur across franchises, so location does not need to be in the same franchise entity as the transfer to locations.
Commissary supply locations. Commissary orders can occur across franchises, so location does not need to be in the same franchise entity as the supply location.
Inventory data copied from the old location
Current on hand quantities. Users in the destination location will not need to enter a physical inventory to start their operations.
Location products, including location products created for prep recipes.
Storage locations, including prep station relationships.
Local product templates, including customer/template links.
Purchasing data copied from the old location
Open vendor orders. This includes orders that are submitted, but have not been reconciled.
Sales data copied from the old location
Current and future sales forecasts.
One year of historical register sales (sales mix).
Labor data copied from the old location
-
Active, on leave, and terminated employees (when termination date is equal to or greater than FCO date). All employees will be marked as ‘New'.
Employees at the destination site with the same employee number, payroll ID, or social security number will not be copied. These are assumed to be the same person.
Employee primary location, employee positions, and employee availability.
Current and future labor schedules.
Employee Teamworx accounts. Employees will need to use the new URL when the sign in.
Local staffing level templates. A local templates will also be created for any corporate staffing level template linked to the old location.
Data copied from the sister location
The following information is copied from the sister location, in the destination site, to the new location, in the destination site.
Calendar data copied from the sister location
-
Scheduled Close, Holiday, Promotion and Post calendars. There will be one posted period, and post periods that match the sister location for current and future periods.
If a sister location is not selected, then Current/Future Post Dates will be created based on the destination Reporting Calendars. In this case Scheduled Close, Holiday, and Promotion Calendars will not be created.
If there is no sister location, the Reporting Calendar must be set up in the destination, or the transfer will not be able to proceed.
Location data copied from sister location
User Defined Categories. The old location is not removed from existing UDCs in the source franchise.
The new location is linked to any corporate product templates the sister location was linked to
Hierarchy data is copied from the sister location
New location is added to any corporate or destination franchisee owned hierarchies that include the sister location.
Labor data copied from sister location
New location is added to any franchise corporate staffing level templates. The old location will not be removed from any corporate staffing level templates.
Data that is created or changed
The following data is created or updated by Crunchtime Support during the Franchise Change of Ownership process.
Location data that is changed
Old location name and code is updated to a value defined by the customer.
The old location is no longer available as a Transfer To location.
Calendar data that is created
A single posted period is created in destination site. The next post day is the post date greater than or equal to the current date (transfer date). Post dates will only be created for the current fiscal year.
Application User data that is changed
Corporate application users (active and inactive) linked to the old location are linked to the new location, so long as they are also linked to the destination site.
Users with the “Link to All Locations” user group permission will be linked to the new location.
Labor data that is changed or created
-
All employees are marked as ‘New’ in the new location.
If the destination site has employee checklist items, those must be completed. The new location will be allowed to schedule incomplete employees for this reason.
Inventory data that is changed or created
A local template is created for any corporate templates linked to the old location.
Data that is not copied
Inventory data that is not copied
Storage sequence in Inventory Setup.
Location products are excluded if they are linked to Concepts that do not include the destination location.
Purchasing data that is not copied
Reconciled vendor orders. Closed vendor orders and historic purchasing reports can be accessed from consolidated reports.
Sales data that is not copied
Menu mix data is not copied during this process, unless otherwise specified. The recommendation is to specify the number of weeks to reference for historical consumption when submitting the FCO request. Another option is to borrow consumption from another location.
Labor data that is not copied
Employee alternate locations. Only the primary location is copied.
Past Teamworx schedules.
Employee photos in Teamworx.
Note: This data is note deleted and can still be access from the source site, unless otherwise specified.
POS integration enablement
The POS Integration feed to the old location will be shut off prior to the transfer starting. Once the transfer is complete, and Support has tested the location, the feed will be enabled to the new location. Support will then repoll the following:
Menu Mix for the current week.
Time Punch records for the current week.
Note: Sales mix data is pulled in by the Franchise Change of Ownership process and will not be repolled.
Comments
0 comments
Please sign in to leave a comment.