Table of Contents

Franchises are a special use of the system that is of interest for many businesses - there are some key concepts that you need to consider.

Which company is your Franchisor?

Changes when you have a franchisor - Shuttle businesses

1. The services on Host Company Booking Services and Fees are inherited from the franchisor and cannot be changed by you on your host company

Franchise Regions

Franchise regions and their owners are defined here.  Each Region can own multiple Areas.

Areas in a Franchise Region

Areas share pricing levels - group suburbs that share pricing into an area.

An Area can only be owned by one franchise

• If an Area is serviced by multiple franchises then will be no franchise owner.

A Suburb can only exist in one Area

Can franchises see each others customers?

This is a decision for the individual business and will affect their privacy policy - inform us of the rules you would like to enforce.

If a Customer (Person or Company) is a Debtor of any franchisee or franchisor they will have a debtor record in that Host Company (same for Creditors).

The system can be configured to

1. Allow all franchisees to see all customer details
2. Allow franchisees to only see their own customers details

External Parters of the Organisation (eg Delegates)

A special type of organisation is one that does work for you or receives work from you.  These are known as Delegates.  

Delegates are normally local to a franchise - so even though the companies are global - the commission rates are set at the Franchisee level

If you have jobs or bookings that you delegate to others - they are suppliers to you - setup the commission % Rate or $ amount on the Supplier (Creditor) for jobs you pass to them

if you have jobs or bookings that others delegate to you - they are a customer of yours - setup the commission % Rate or $ amount on the Customer (Creditor) for jobs they pass to you.

Employees

Employees may use different menus for the different systems - the best way to achieve this is the person to have multiple employee records - this is best shown through an example.

Paul has two employee records - note that each employee record is a different login code....

Why have multiple employee records?

1. Be logged into more than one Host Company at once.
2. Each login will have different menus
   1. This is key for users that want different menus in different companies

Pricing

Some franchises will price globally and some will price locally (to account for local conditions).

The system remembers where the booking/order pricing is initially taken from and any changes will continue to use that pricing.

If the customer is on a central franchise website

1. Before pricing the system will attempt to determine if the customer Area is owned by a franchise - if it is pricing comes from the pricing defined in the franchise and the order/booking will be placed directly into that Host Company
2. If the customer is not in an owned franchise Area - the system will prompt the logged in user if they want the order/booking in their Franchise Host Company.
   
   1. If yes - then pricing is from the Franchisor (as no franchisee pricing will exist) - however the booking will be placed into the users logged in company (in our example a franchisee) Host Company (along with associated invoice/payment if made at that time)
   2. if no - then the Franchisor pricing will be used and the booking will be placed into the Franchisor Host Company (along with associated invoice/payment if made at that time)

If the customer is talking to a logged in user and they are logged into a particular Host Company (eg a franchisee)

1. Before pricing the system will attempt to determine if the customer Area is owned by a franchise - if it is pricing comes from the pricing defined in the franchise and the order/booking will be placed directly into the Host Company for the Franchise Owner
2. If the customer is not in an owned franchise Area - the system will prompt the logged in user if they want the order/booking in their Franchise Host Company.
   1. If yes - then pricing is from the Franchisor (as no franchisee pricing will exist) - however the booking will be placed into the users logged in company (in our example a franchisee) Host Company (along with associated invoice/payment if made at that time)
   2. If no - then pricing is from the Franchisor (as no franchisee pricing will exist) - however the booking will be placed into the Franchisor Host Company (along with associated invoice/payment if made at that time)

Movement of customer requests (Orders/Bookings)

If a customer Order/Booking is moved from one Host Company to another - the system remembers the host company that was used for the original pricing and will use that pricing for changes.

This is to avoid the pricing being changed markedly from the customer perspective if a different franchise is now dealing with the customer request.

For example

1. Franchise A takes a customer request in their franchise area - their pricing is used
2. The request is moved for some reason to another franchise
3. The customer request is changed in some way - the system will use the pricing from the original franchise for the changes (if possible)