Beruflich Dokumente
Kultur Dokumente
The information contained in this document is current as of the date of publication and subject to change. Because Tally must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Tally, and Tally cannot guarantee the accuracy of any information presented after the date of publication. The information provided herein is general, not according to individual circumstances, and is not intended to substitute for informed professional advice. This document is for informational purposes only. TALLY MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT AND SHALL NOT BE LIABLE FOR LOSS OR DAMAGE OF WHATEVER NATURE, ARISING OUT OF, OR IN CONNECTION WITH THE USE OF OR INABILITY TO USE THE CONTENT OF THIS PUBLICATION, AND/OR ANY CONDUCT UNDERTAKEN BY PLACING RELIANCE ON THE CONTENTS OF THIS PUBLICATION. Complying with all applicable copyright and other intellectual property laws is the responsibility of the user. All rights including copyrights, rights of translation, etc., are vested exclusively with TALLY SOLUTIONS PRIVATE LIMITED. No part of this document may be reproduced, translated, revised, stored in, or introduced into a retrieval system, or transmitted in any form, by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Tally Solutions Pvt. Ltd. Tally may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written licence agreement from Tally, the furnishing of this document does not give you any licence to these patents, trademarks, copyrights, or other intellectual property. 2010 Tally Solutions Pvt. Ltd. All rights reserved. Tally, Tally 9, Tally9, Tally.ERP, Tally.ERP 9, Shoper, Shoper 9, Shoper POS, Shoper HO, Shoper 9 POS, Shoper 9 HO, TallyDeveloper, Tally Developer, Tally.Developer 9, Tally.NET, Tally Development Environment, Tally Extender, Tally Integrator, Tally Integrated Network, Tally Service Partner, TallyAcademy & Power of Simplicity are either registered trademarks or trademarks of Tally Solutions Pvt. Ltd. in India and/or other countries. All other trademarks are properties of their respective owners. Version: Chain Store Implementation/1.0/February 2010
Contents
Introduction Implementation Presales ................................................................................................................................................. 3
Standard Product Demo ..................................................................................................................................... 4
Conference Room Pilot (CRP) ............................................................................................................... 5 Pilot run at Chosen Locations ................................................................................................................ 6
User Acceptance Testing ...................................................................................................................... 6
Introduction
Chain stores are retail outlets that share a brand and are centrally managed and usually have common business processes and practices. In the chain store scenario, the retail components consist of, POS/Store locations Company Stores Franchisee Stores Consignment Stores Buy & Sell Stores Distributors Head Office Chain stores can be classified as: Own stores (Company owned):These are owned by the retail company operating the chain. They receive goods from the Suppliers/Vendors on a transfer or consignment basis at the companys distribution locations. The stock items are owned by the company and will be transferred to the company showrooms. The personnel working in a company owned showroom are employed by it. Operationally, they are controlled and answerable to the head office of the company. Franchisee or Buy & Sell stores:These are entities which sell goods supplied by the retail company either on agreed or own terms. They purchase the goods from the Distributors/Vendors as per agreement with the head office. The stock ownership rests with the franchisee while the operations may be subject to a minimum control by the head office. There may be franchisee stores stocking and selling items which are owned by the company. Following are the business activities supported by Shoper 9 in a chain store scenario: Store is a part of a chain/network controlled by a head office. The Vendor supplies goods directly to the POS locations, head office makes the payment and tracks goods. The Vendor supplies goods to the companys Distributor and the Distributor sends them to POS locations. Head office makes the payment and tracks the goods. There is constant communication between the HO and other constituents of the chain. The data management of the retail chain is centralised at the head office. The stores data is consolidated, replicated at the head office and analysed for decision making (MIS) and execution of future policies. Head office is only a facilitator and does not transact data but functions as a supervisor of the chains activities.
Introduction
Implementing Shoper 9 in a chain store scenario requires proper understanding of the customers business needs, good planning and proper execution. Mentioned below are the recommended best practices to be followed for a successful implementation in a chain store scenario. Presales Standard Product Demo Understanding Customer Requirements Design and Construct solution Customisation (if required) Conference Room Pilot Pilot run at chosen locations User Acceptance Testing Implementation rollout in all locations End User Training Help and Support Post Implementation Activities Post implementation support (limited period) Implementation closure Further support services and maintenance
However, all activities mentioned are not compulsory in all implementations. An activity like the conference room piloting depends on the request and agreement with the customer.
1. Implementation
1.1 Presales
Presale is the first activity where you will be prepared to engage with the prospective client. It is a process or a set of activities normally carried out before a customer is acquired, though sometimes the activity extends into the period the product or service is delivered to the customer. The activities include the following: Meet the client and discuss the requirements. Gather information on their past experience, current business lines, product range, physical & IT infrastructure, people, etc. Find the customers expectations from Shoper 9. Appraise them of our past experience and organisational capability as a solution provider to retail chains. Impress on the service aspect in terms of our office network, partner network, support structure, satisfied customers, etc. Highlight on the integrated offering of Shoper 9 with Tally.ERP 9 for managing both retail and accounting operations of the client. Check if the client has other applications which are to be integrated with Shoper 9. Provide approximate cost of Shoper 9 deployment based on the number of stores distributors, vendors and the requirements at head office. Arrange for a standard product demo. Note: All documents/tools referenced in this guide are available on the Partner Portal of Tally website.
Implementation
Implementation
For details, refer the Requirement Study and Configuration Tool document which provides the facility and flexibility to gather clients requirement in a questionnaire format.
Implementation
Implementation
Serial No
1 2 3 4 5
Tool
Shoper 9 CD Shoper 9 CD Shoper 9 CD Custom LiveUpdate location & patches H/W & S/W Readiness Checklist
Responsibility
Customer Implementer Implementer Implementer Customer
The Shoper 9 Custom Installer has to be prepared to ensure that the approved customer specific business template and the customisations can be deployed in the rollout locations. Please refer Shoper 9 POS Customised Installer.pdf for the creation and deployment of Custom Installer. Refer the Implementation and Training Checklist for Rollout document to get the implementation sign off from the customer.
Implementation
Implementation
Implementation Closure
Finally, secure a sign off that the product has been successfully implemented in the locations. (Refer Project Sign off Document)
Implementation
Take the sign off after a successful pilot run and provide a rollout plan Collect the implementation and training checklist from all locations where Shoper 9 implementation has been done Plan for post implementation support period depending on the customer installation size Collect the project sign off after the completion of the implementation (Use Project Sign Off Document)
10