Wegrzyn, John (Bonnet Bay, AU)
Levine, Dave (Matraville East, AU)
Abundo, Arnold (Padstow, AU)
Kumar, Shon (Cremorne, AU)
Plaque It!
|
2. The system as claimed in claim 1, wherein electronic processing of returned goods is integrated into an order tracking procedure.
3. The system as claimed in either claim 1 or claim 2, wherein the Supplier is a FMCG Manufacturer or a Wholesaler.
4. The system as claimed in any one of the claims 1 to 3, wherein the system includes a centrally managed database which is linked with the Supplier ordering system.
5. The system as claimed in any one of the claims 1 to 3, wherein POS/BOS data is managed within a centrally managed database.
6. The system as claimed in any one of the claims 1 to 5, wherein goods are scanned on receipt by the Convenience Retailer and/or on sale to a consumer.
7. The system as claimed in any one of the claims 1 to 6, wherein the associated data is used to deliver market information to the Convenience Retailer, the Supplier, a Manufacturer, a Wholesaler or a Logistics Provider.
8. The system as claimed in claim 7, wherein the system provides network-based access to the market information via a business-to-business web portal.
9. The system as claimed in any one of the claims 1 to 8, wherein part of the system is in a private network and access to the part of the system requires user authentication.
10. The system as claimed in any one of the claims 1 to 9, wherein the system includes means for Available To Promise (ATP) checking from the Supplier's inventory database.
11. The system as claimed in any one of the claims 1 to 10, wherein the system includes means for providing electronic confirmation of replenishment order acceptance from the Supplier to the Convenience Retailer.
12. The system as claimed in any one of the claims 1 to 11, wherein the system includes means for electronic tracking of replenishment orders until delivery of the goods to the Convenience Retailer.
13. The system as claimed in any one of the claims 1 to 12, wherein all electronic transfers and ordering occur via the Internet.
14. An integrated system for providing an electronic marketplace solution, the system including: means for Point of Sale (POS) scanning of goods and associated data capture by a Convenience Retailer; means for a Convenience Retailer to search and browse a multiple Supplier goods and pricing catalogue for determining a replenishment order for goods; means to provide the Convenience Retailer with online replenishment order placement to a Supplier; means for the tracking and management of goods; means for providing electronic bill presentation and payment; and, means to generate customised reports for the Convenience Retailer or the Supplier.
15. The system as claimed in claim 14, wherein the system includes means to facilitate Supplier access to marketplace based promotions.
16. The system as claimed in claim 14, wherein the system includes a telecommunications infrastructure providing: a secure private network; a secure connection via the Internet; and Internet connectivity.
17. The system as claimed in any one of the claims 14 to 16, wherein the system includes inventory management and business reporting tools for the Convenience Retailer.
18. The system as claimed in any one of the claims 14 to 17, wherein the system is integrated with at least one Supplier enterprise resource planning (ERP) system to provide: Available To Promise (ATP) checking from the Supplier's inventory database; credit and payment status checking from the Supplier's financial database; electronic transfer of orders to the Supplier's order capture system; and Supplier confirmation of order acceptance and fulfilment.
19. The system as claimed in any one of the claims 14 to 18, wherein the system communicates with commercial banking systems to provide the electronic payment.
20. The system as claimed in any one of the claims 14 to 19, wherein the system includes business and technology integration with convenience industry Service Providers to promote and supply related goods or services.
21. A method of providing an electronic marketplace solution, the method including the steps of: a Convenience Retailer performing Point of Sale (POS) scanning of goods and associated data capture; determining a replenishment order for goods, based on sales by the Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods; electronically transferring the replenishment order to a Supplier via a Supplier ordering system; an automated request being transmitted, by a Convenience Retailer terminal or the Supplier ordering system, to a Logistics Provider to effect delivery of the goods; the Logistics Provider arranging delivery of the goods to the Convenience Retailer; and, performing payment processing which links the Supplier ordering system and a payment gateway which is able to communicate with the Convenience Retailer's commercial banking system.
22. The method as claimed in claim 21, wherein the Convenience Retailer terminal can be used to access a database providing the delivery status of the goods.
23. The method as claimed in claim 21, wherein goods are scanned by the Convenience Retailer, the Supplier and the Logistics Provider, thereby providing marketplace information able to be accessed in a database.
24. The method as claimed in claim 23, wherein goods are scanned by a scanner connected to the Convenience Retailer terminal when received by the Convenience Retailer, thereby updating relevant records in the database.
25. The method as claimed in claim 21, wherein relevant records include: inventory information; sales figures; time of sale; place of sale; or identifying information about the consumer.
26. The method as claimed in any one of claims 21 to 25, wherein information pertaining to consumer purchases gathered by the Convenience Retailer is visible to the Supplier; a Wholesaler; the Logistics Provider; and/or a Service Provider.
27. The method as claimed in any one of claims 21 to 26, wherein automated ordering of goods occurs when database records indicate that the Convenience Retailer's stock of goods is at a predetermined level.
28. The method as claimed in any one of claims 21 to 27, wherein the Supplier, a FMCG Manufacturer, a Wholesaler, a Logistics Provider, and/or a Service Provider, individually or cooperatively collate orders for goods from the Convenience Retailer.
29. The method as claimed in any one of claims 21 to 28, wherein data or information pertaining to past sales transactions in the convenience marketplace are available, via a computer network, to authorised users or participants from an information source.
30. A network based business to business Internet portal, the Internet portal providing access to an electronic marketplace solution, the Internet portal providing: a facility to submit a replenishment order to a Supplier via a Supplier ordering system, the replenishment order based on sales of goods by the Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods; a facility for the Supplier to confirm the availability of goods; a facility to provide goods delivery status information; and, a payment processing system which links the Supplier ordering system and a payment gateway which is able to communicate with the Convenience Retailer's commercial banking system allowing the Convenience Retailer to pay for goods.
31. A set of computer readable medium of instructions for use in providing an electronic marketplace solution, the set of instructions enabling web-based order processing and including procedures for: Point of Sale (POS) scanning of goods and associated data capture; determining a replenishment order for goods, based on sales by a Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods; electronically transferring the replenishment order to a Supplier via a Supplier ordering system; and, web-based browse and buy functionality providing payment processing which links the Supplier ordering system and a payment gateway which is able to communicate with the Convenience Retailer's commercial banking system.
32. The set of instructions as claimed in claim 31, wherein the procedures also include available To Promise (ATP) checking from the Supplier's inventory database, and Supplier confirmation of the replenishment order acceptance.
TECHNICAL FIELD
[0001] The present invention relates to a new type of network based business to business portal, and in particular, to a method of, system for, or computer readable medium of instructions for, providing a new type of Internet based business to business portal for the retail convenience marketplace.
BACKGROUND ART
[0002] Presently, the Australian retail convenience store market is estimated to generate annual revenues of AUD$10bn—AUD$12bn and consist of up to 60,000 outlets of which 75% are classified independent stores and 25% organised stores. The supply chain to this large number of retail outlets is costly and largely inefficient due to a high level of independent ownership and market fragmentation. This problem exists in many other retail convenience store marketplaces throughout the world.
[0003] The four key participants/groups involved in the convenience marketplace include:
[0004] Convenience Retailers—includes Organised Convenience, Independent Convenience/Route, Specialty Stores and Independent Supermarkets and Grocers;
[0005] Fast Moving Consumer Goods (FMCG) Manufacturers—includes Suppliers whose products are purchased by Convenience Retailers;
[0006] Wholesalers/Logistics Providers—includes any businesses providing product distribution services to Convenience Retailers and for FMCG Manufacturers;
[0007] Service Providers—includes any businesses providing “not for on-sale” products and services to Retailers, FMCG Manufacturers and/or their staff.
[0008] This supply chain and process complexity identifies a need to provide Retailers and Manufacturers, inter alia, a means to increase overall supply chain effectiveness.
[0009] There is a need to address the key business issues faced by the Convenience Retailer and to offer a solution which provides real value. A solution should have the ability to address the needs of key participants in the retail convenience store supply chain. These participants include Convenience Retailers, FMCG Manufacturers, Wholesalers/Logistics Providers and Service Providers.
[0010] Convenience Retailers:
[0011] The Retailer channels are generally those where consumer purchases are largely impulse or for immediate consumption. These channels include, but are not exclusive to, Organised Convenience, Independent Convenience/Route, Newsagents, Independent Grocery and Specialty Stores. There exists a need to provide such Retailers with a convenient means of accessing, ordering, handling payments, recording, managing and/or the like, goods, supplier details and/or other aspects of a Retailer's trade.
[0012] FMCG Manufacturers:
[0013] As an illustrative example, AC Nielsen estimates that at least 65% of the Australian convenience store market is supplied by fewer than ten manufacturers. Sales by individual manufacturers to these convenience stores can range from 5% of total deliveries (generally dry grocery products) to 50% (commonly impulse brand products such as chocolate bars, tobacco products and soft drinks). There exists a need to provide FMCG Manufacturers with a convenient means of supplying, offering for supply, ordering, arranging delivery, recording, managing, handling payments, and/or the like, goods, customer's details and/or other aspects of a Manufacturer's trade.
[0014] Wholesalers/Logistics Providers:
[0015] In Australia, approximately 25% of products sold in convenience stores are sourced through Wholesalers. The current wholesale market is characterised by various organised groups with differing operating arms and formats and a lack of a single nationwide organisation. There exists a need to provide a single portal for the various Wholesalers to reach the targeted Retailers.
[0016] Logistics Providers include businesses providing deliveries (and associated services) to the targeted Retailers. Industry consolidation in the Australian market, for example, has, at present, left only a few major players. There exists a need to provide a single portal for Logistics Provider's to reach/service the targeted Retailers, Wholesalers and/or Manufacturers.
[0017] There exists a need to provide Wholesalers and/or Logistics Providers with a convenient means of supplying, offering for supply, ordering, arranging delivery, recording, managing, handling payments, tracking and optimising logistics, and/or the like, goods, customer's details, supplier's details and/or other aspects of a Wholesaler's and/or Logistics Provider's trade.
[0018] Service Providers:
[0019] There are a number of organisations providing products and services (not for on-sale) to Retailers, FMCG Manufacturers, and/or their staff. These include providers of banking and insurance services, building and maintenance products, telecommunications services and lifestyle products. There exists a need to allow these providers to offer additional services to Retailers, Wholesalers, Logistics Providers and/or Manufacturers through a business exchange mechanism in an efficient manner.
[0020] Within the Retail Industry, it is presently known to individually provide:
[0021] Point of Sale (POS) scanning, that is sales information capture; or
[0022] Calculation of a replenishment order based on sales; or
[0023] Electronic transfer of store order to a web ordering site; or
[0024] Integration of a store order to web-based browse and buy functionality.
[0025] However, the combination of these features to provide an electronic marketplace solution, which in a non-limiting form may be embodied, at least partly, as a software marketplace solution, is not presently known and represents a problem to be overcome for the benefit of the convenience retail industry.
[0026] Presently, the following systems, individually, are available as stand-alone systems within the retail industry:
[0027] Available To Promise (ATP) checking from supplier's inventory database; or
[0028] Electronic transfer of checked order to supplier's order capture system; or
[0029] Supplier confirmation of order acceptance and fulfilment.
[0030] However, the combination of these systems to provide an electronic marketplace solution, which in a non-limiting form may be embodied, at least partly, as a software marketplace solution, is not presently known and represents a problem to be overcome for the benefit of the marketplace. This identifies a need to provide an end to end process for the order capture and order fulfilment within an e-commerce electronic marketplace solution for the convenience retail industry.
[0031] Furthermore, the integration of electronic payment processing with a combination of the aforementioned services/systems is, to the Applicant's knowledge, not presently known. There exists a need for a new integrated system of electronic payment processing provided with a combination of the aforementioned functions.
[0032] Presently, the provision of valued information regarding goods purchases by consumers to all or part of the convenience retail industry, that is, for example, manufacturers, store owners, wholesalers and logistics providers, is significantly limited. There exists a need to provide an improved means to obtain, access, manage and/or distribute this information.
[0033] Definitions:
[0034] The term “supplier” should be taken as a reference to the manufacturer, distributor or wholesaler selling the products to the retailer.
[0035] In a networked data communications system, users have access to terminals which are capable of requesting and receiving information from local or remote information sources. In such a system a terminal may be any type of computer or computerised device, a personal computer (PC), a mobile or cellular phone, a mobile data terminal, a portable computer, a personal digital assistant (PDA), a pager, a thin client, or any other similar type of electronic device. The capability of the terminal to request and/or receive information can be provided by an application program, hardware or other such entity. A terminal may be provided with associated devices, for example an information storage device such as a hard disk drive.
[0036] In such a system an information source may be a server or any other type of terminal (for example, a PC computer) coupled to an information storage device (for example, a hard disk drive). The exchange of information (i.e., the request and/or receipt of information) between the terminal and the information source, or other terminal(s), is facilitated by a connection referred to as a communication channel. The communication channel can be physically realised via a metallic cable (for example, a telephone line), semi-conducting cable, an electromagnetic signal (for example, a radio frequency (RF) signal), an optical fibre cable, a microwave link, a satellite link or any other such medium or combination thereof connected to a network infrastructure.
[0037] The infrastructure may be a telephone switch, a base station, a bridge, a router, or any other such specialised component, which facilitates the connection between the terminal and the network. Collectively, the interconnected group of terminals, physical connections, infrastructure and information sources is referred to as a computer network or data communications network.
[0038] The computer network itself may take a variety of forms. It may be located within a local geographic area, such as an office building, and consist of only a limited number of terminals and information sources. This type of computer network is commonly referred to as a Local Area Network (LAN). On a broader scale, it may be larger and support more users over a wider geographic area, such as across a city. This type of network is commonly referred to as a Wide Area Network (WAN). On an even broader scale LAN and WAN networks may be interconnected across a country or globally. An example of a globally connected computer network is the Internet.
[0039] To a user the Internet appears to be a single unified computer network, although in reality it consists of many different types of computer platforms utilising many diverse data communications technologies. The technologies are connected together in such a manner so they appear transparent to the user. This transparency is made possible through the use of a standard communications protocol suite known as Transmission Control Protocol/Internet Protocol (TCP/IP).
[0040] The Hyper-text Mark-up Language (HTML) and Hyper-text Transfer Protocol (HTTP) have developed to make the Internet or World Wide Web very accessible. The exchange of information on the Internet is further facilitated through hyper-text documents. Hyper-text documents are unique in that they use tags to define links which, when selected, fetch the related information from within the same document or from a new document altogether. The links are defined using HTML which provides a document formatting method which adapts in a consistent manner to any computer on which it is displayed. HTML tags are used to define the various components of an ASCII text file, image or sound which make up a hyper-text document, including such things as formatting and linking to other documents. HTML tags which link documents on one Internet information source to those on another do so by associating a Uniform Resource Locator (URL) with the referenced information. The ability to link Internet files of similar and/or differing formats to each other, and to link documents on other Internet sites, is a powerful feature of the Internet.
[0041] The appeal of the Internet is the large-scale interconnection of public and private networks. A concern exists, however, about “unauthorised” access from public networks to the attached private networks. This concern has resulted in the development of proxies. A proxy is a host computer or mechanism (usually an application program) on a network node which performs specialised functions on a network. One such function is to provide network security. Security is provided between a private and public network by requiring communications (i.e., information exchanges) to pass through the proxy. Another function of a proxy is to store or cache recently accessed information (i.e., copies of documents and images). If a browser desires information which is located outside the local network, that is to say on an information source attached to an external network, communications pass from the browser through the proxy before going on to the external network. Thus a proxy may operate to deny access to a private network from a public network by not replying to HTTP commands received from the public network.
[0042] Files are stored at various information sources. A user can access files from an information source, if authorised, by connecting to a computer network and requesting the files for viewing or downloading. Financial transactions are provided for over the computer network. Typically, financial transactions utilise proxies, SSL, data encryption etc.
[0043] Glossary of Terms:
B2B Business to Business BOS Back Office System Convenience Includes Convenience Retailers, Fast Moving marketplace Consumer Goods (FMCG) Manufacturers, Wholesalers and Logistics Providers, Service Providers Connectivity The ability to efficiently transfer data/information Development software A software platform providing the framework for an embodiment of the present invention eBPP Electronic Bill Presentment and Payment ERP Enterprise Resource Planning FMCG Fast Moving Consumer Goods Independent A Convenience Retailer not belonging to a Convenience group of Retailers Retailers Internet Portal A web-site positioned as an entrance in the Internet to a service or variety of services Organised A Convenience Retailer belonging to a group of Convenience Retailers Retailers Participants Include Retailers, FMCG Manufacturers, Wholesalers/Logistics Providers and Service Providers POS Point of Sale Scanner Device used to obtain information/data associated with a particular product or good Specialty Stores Retailer having a specialised range of goods Supply Chain Hierarchy of movement of goods within the convenience marketplace Third Party Software Additional software ancillary to the development software required for an embodiment of the present invention Virtual Private A secure shared network, eg. secured by Network encryption, tunnelling, firewalls etc.
[0044] This identifies a need for a new type of method of, system for, or computer readable medium of instructions for, providing a new type of Internet based business to business portal for the convenience marketplace which overcomes or at least ameliorates the problems and limitations inherent in the prior art.
DISCLOSURE OF INVENTION
[0045] Broadly, the present invention provides an Electronic Marketplace Solution (EMS) which may be embodied, in part or in whole, as a method, system or computer readable medium of instructions.
[0046] The present invention seeks to provide a business to business Internet portal, which may be independent, serving companies operating within the convenience marketplace, for example within Australia and New Zealand, specifically the present invention seeks to increase operational efficiency and effectiveness for all, or at least some, participants.
[0047] In a non-limiting embodiment of the present invention, the present invention seeks to provide an Internet portal to deliver the opportunity for significant business improvement to, inter alia:
[0048] Independent Convenience Retailers through the provision of a single system, method, and/or an electronic marketplace solution to sell, buy and pay for goods/services and manage their business more effectively; and/or
[0049] Organised Convenience Groups, by providing them access to improved network management, the ability to ensure compliance and the ability to reduce costs; and/or
[0050] FMCG Manufacturers in the areas of secondary supply chain efficiencies, improved business intelligence and direct access to Convenience Retailers; and/or
[0051] Wholesalers/Logistics Providers, for reduced costs and improved efficiency and enabling them to expand their customer base; and/or
[0052] Service Providers, by enabling them to more efficiently reach a large target market.
[0053] In a preferred embodiment, the present invention seeks to provide an electronic marketplace solution which takes sales-based orders through to a shopping cart function for web-based order processing, which includes:
[0054] Point of Sale (POS) scanning, that is sales information capture;
[0055] Calculation of a replenishment order based on sales;
[0056] Electronic transfer of store order to a web ordering site; and
[0057] Integration of a store order to web-based browse and buy functionality.
[0058] In another preferred embodiment, the present invention seeks to provide an electronic marketplace solution which integrates:
[0059] Available To Promise (ATP) checking from supplier's inventory database;
[0060] Electronic transfer of checked order to supplier's order capture system,
[0061] Supplier confirmation of order acceptance and fulfilment; and
[0062] whereby links between the electronic marketplace solution's browse and buy functionality and the supplier's sales systems are provided, enabling online tracking of web-placed orders.
[0063] In a further preferred embodiment, the present invention seeks to provide an electronic marketplace solution which integrates:
[0064] Sales-based orders being placed through to a shopping cart function for Web-based order processing, including:
[0065] Point of Sale (POS) scanning;
[0066] Calculation of a replenishment order based on sales;
[0067] Electronic transfer of store order to a web ordering site; and
[0068] Integration of a store order to web-based browse and buy functionality; and
[0069] ATP checking from supplier's inventory database;
[0070] Supplier confirmation of order acceptance and fulfilment;
[0071] Electronic transfer of checked order to supplier's order capture system; and
[0072] whereby links between the electronic marketplace solution's browse and buy functionality and the supplier's sales systems are provided, enabling online tracking of web-placed orders.
[0073] In a further particular embodiment of the present invention, electronic processing of claims is integrated in the electronic marketplace solution. Preferably, but not necessarily, the electronic marketplace solution includes a centrally managed data library which is linked with the order processing system; Also, POS/BOS data can be managed within a central service, thereby increasing the accuracy of information across retail stores as well as reducing retail store level administration requirements. In a particular embodiment of the present invention, the data is managed to deliver valued information to all or some of the marketplace solution members, that is, for example, manufacturers, store owners, wholesalers and logistics providers to the retail trade. Preferably, the electronic marketplace solution can provide access to this managed information relating to consumer purchases via a business-to-business web portal. In a particular embodiment of the present invention, it is sought to provide a web-site for the Logistics Providers to access information pertaining to the targeted Retailers.
[0074] In a further embodiment of the present invention, there is provided an integrated system for providing an electronic marketplace solution, the integrated system including:
[0075] means for Point of Sale (POS) scanning of goods and associated data capture by a Convenience Retailer;
[0076] means for determining a replenishment order for goods, based on sales by the Convenience Retailer, preordained Convenience Retailer criteria, or the Convenience Retailer manually selecting goods;
[0077] means for the electronic transfer of the replenishment order to a Supplier Internet-based ordering system; and
[0078] means for integration of the replenishment order to Internet-based browse and buy functionality on the Supplier Internet-based ordering system.
[0079] In a further embodiment of the present invention, there is provided an integrated system for providing an electronic marketplace solution, the integrated system including:
[0080] means for the electronic transfer of a Convenience Retailer's replenishment order of goods to a Supplier's ordering capture system;
[0081] means for Available To Promise (ATP) checking from the Supplier's inventory database;
[0082] means for providing electronic confirmation from the Supplier of replenishment order acceptance to the Convenience Retailer; and
[0083] means for electronic tracking of replenishment orders until delivery of the goods to the Convenience Retailer.
[0084] In a further embodiment of the present invention, there is provided a system for providing an electronic marketplace, the system including:
[0085] means for a Convenience Retailer to search and browse a multiple Supplier goods and pricing catalogue;
[0086] means to provide the Convenience Retailer with online order placement, tracking and management of goods;
[0087] means to generate customised reports; and
[0088] means for electronic bill presentation and payment.
[0089] According to another possible aspect, means are also provided to facilitate Supplier access to marketplace based promotions is provided. Also the system may include a telecommunications infrastructure providing: a secure private network; a secure connection via the Internet; and Internet connectivity. According to another aspect, the system includes Point of Sale (POS) scanning of goods, and inventory management and business reporting tools for the Convenience Retailer.
[0090] In a further possible form, the system is integrated with Supplier enterprise resource planning (ERP) systems to provide:
[0091] Available To Promise (ATP) checking from the Supplier's inventory database;
[0092] credit and payment status checking from the Supplier's financial database;
[0093] electronic transfer of orders to the Supplier's order capture system; and
[0094] Supplier confirmation of order acceptance and fulfilment. Preferably, the system communicates with commercial banking systems to provide electronic payment and funds transfer facilities.
[0095] In a further embodiment of the present invention, there is provided a method of providing an electronic marketplace solution, the method including the steps of:
[0096] a Convenience Retailer identifying, on a Convenience Retailer terminal, goods which the Convenience Retailer desires to purchase, via a computer network portal, the goods being offered by a Supplier on a Supplier ordering system;
[0097] the Convenience Retailer requesting, on the Convenience Retailer terminal, the purchase and delivery of the goods;
[0098] a request being transmitted, by the Convenience Retailer terminal via the computer network, to the Supplier ordering system for the requested goods;
[0099] an automated request being transmitted, by the Convenience Retailer terminal or the Supplier ordering system, to a Logistics Provider to effect delivery of the goods; and
[0100] the Logistics Provider arranging delivery of the goods to the Convenience Retailer, whereby the Convenience Retailer terminal can be used to access goods delivery status information on a database.
[0101] In a further embodiment of the present invention, there is provided a network based business to business Internet portal, the Internet portal facilitating network communication between:
[0102] a Convenience Retailer; and
[0103] a Supplier; and
[0104] a Wholesaler or Logistics Provider; and whereby, the Internet portal is used to allow functions including:
[0105] the Convenience Retailer to order and pay for goods or services; and
[0106] the Supplier to confirm the availability of goods; and
[0107] the Logistics Provider to provide tracking of goods delivery status.
[0108] In a further embodiment of the present invention, there is provided a set of computer readable medium of instructions for use in providing an electronic marketplace solution, the set of instructions enabling web-based order processing and including procedures for: Point of Sale (POS) scanning of goods at a Convenience Retailer; calculation of a replenishment order based on sales by the Convenience Retailer; electronic transfer of the replenishment order to a web-based ordering site; and web-based browse and buy functionality for Convenience Retailer's goods orders.
[0109] In a further embodiment of the present invention, there is provided a set of computer readable medium of instructions for use in providing an electronic marketplace solution, the set of instructions enabling web-based order processing and including procedures for: Available To Promise (ATP) checking from a Supplier's inventory database; electronic transfer of orders from a Convenience. Retailer to the Supplier's order capture system; and Supplier confirmation of order acceptance.
[0110] Preferably, the computer network is the Internet. Also preferably, each terminal is a PC. In a further embodiment of the present invention all transactions, purchases and the like are stored for subsequent access. In a further embodiment of the present invention all goods are scanned by a scanner connected to the Convenience Retailer's terminal when received by the Convenience Retailer, thereby updating relevant records for any of the participants. In still a further embodiment of the present invention all goods are scanned by a scanner connected to the Convenience Retailer's terminal when purchased by a consumer from the Convenience Retailer, thereby updating relevant records for any of the participants. In an embodiment of the present invention, relevant records include: inventory information; sales figures; time of sale; place of sale; identifying information about the consumer; and/or the like. In a further broad form of the present invention, the present invention also provides that information pertaining to consumer purchases gathered by the Convenience Retailer is visible to the FMCG Manufacturer; Wholesaler; Logistics Provider; and/or Service Provider. In still a farther embodiment of the present invention, automated ordering of goods by the Convenience Retailer's terminal occurs when database records indicate that the Convenience Retailer's stock of goods is at a predetermined level. In still a further embodiment of the present invention, the FMCG Manufacturer, Wholesaler, Logistics Provider, and/or Service Provider, can individually or cooperatively collate orders for goods from Convenience Retailer's so that the distribution of goods is efficiently carried out. In still yet a further broad form, the present invention provides that any or all of the participant's terminals reside in a private network and/or access to the computer network portal occurs via a proxy server which may require user authentication. In still yet a further broad form, the present invention provides that data, information and/or files pertaining to past transactions in the convenience marketplace are available, via a computer network, to authorised users or participants from at least one information source.
[0111] In yet a further broad form, the present invention provides that the computer network can be any network of two or more communicating computers or terminals including but not limited to, an internetwork, an intranetwork, a LAN, a WAN, or the Internet. In still yet a further broad form, in accordance with the present invention information or data is exchanged by means including but not limited to: metallic cables; semi-conducting cables; optical fibre cables; satellite links; electromagnetic waves; microwave links; exchanging of memory devices; or any other such medium or combination thereof connected to a network infrastructure.
BRIEF DESCRIPTION OF FIGURES
[0112] The present invention will become apparent from the following description, which is given by way of example only, of a preferred but non-limiting embodiment thereof, described in connection with the accompanying figures, wherein:
[0113]
[0114]
[0115]
[0116]
[0117]
[0118]
[0119]
[0120]
[0121]
[0122]
[0123]
[0124]
[0125]
[0126]
[0127]
[0128]
[0129]
[0130]
[0131]
[0132]
[0133]
[0134]
[0135]
[0136]
[0137]
[0138]
[0139]
[0140]
[0141]
[0142]
[0143]
[0144]
[0145]
[0146]
[0147]
[0148]
[0149]
[0150]
MODES FOR CARRYING OUT THE INVENTION
[0151] The present invention provides a new type of Internet based business to business portal. In a particular embodiment of the present invention, the present invention seeks to address the needs of participants in the Retail Convenience Store supply chain, these participants include Retailers, FMCG Manufacturers, Wholesalers/Logistics Providers and Service Providers. This is illustrated in
[0152] The present invention is designed to provide participants with a means to more effectively manage the growth and profitability of their businesses. For this to be achieved and the benefits of an exchange marketplace to be maximised, participation by a critical mass of Retailers and FMCG Manufacturers will be required. All participants should achieve benefits by subscribing to the business exchange system/method. Cost savings through process optimisation can be achieved in the areas of, for example, order capture, payment, and delivery. Real time business intelligence information and organisational efficiencies can significantly benefit network management, field sales, marketing and manufacturing. In addition, reduced administration workload will free up valuable time for participants to focus on their business.
[0153] The present invention may be applied to any convenience marketplace in the world, although various compliance changes may be required to implement the present invention these compliance changes should be considered to be encompassed by the scope of the present invention.
[0154] Participation in the business exchange system/method of the present invention can provide significant benefits. These benefits may vary depending on whether the participant is a Retailer (organised or Independent) or Supplier (FMCG Manufacturer, Wholesaler/Logistics Provider, or Service Provider).
[0155] The introduction of the overall functionality, may take place progressively over a series of business releases, as shown in
[0156] In a preferred, but non-limiting, embodiment of the invention, the present invention utilises a software development platform to create a computer readable medium of instructions. In this embodiment, development software provides the necessary framework to support the present invention. The key modules of the solution of this embodiment include: Customer Management; Order Management; Demand Fulfilment; Business Intelligence; Replenishment Planner; and eBusiness Framework.
[0157] In addition to the development software, the total solution of this embodiment is dependent on a range of further software, including Electronic Bill Presentment and Payment software and an in-store Point of Sale system.
[0158] An overview of all the key modules is presented below. It should be noted that although development software and further software is described in this embodiment of the present invention, any form of creating or obtaining such software is applicable to the present invention. Numerous alternate software platforms/languages may be utilised to work the present invention.
[0159] A possible B2B solution architecture of an embodiment of the present invention is illustrated in
[0160] Point of Sale:
[0161] The Point of Sale solution (POS) comprises hardware (PC, scanner and/or data capture device) and back office software, which is located within the Retailers store, and hosted software located at a centrally managed facility. At the store level, Retailers can benefit from features including scanning technology, inventory management and sales data analysis. The hosted Point of Sale software can provide Retailers with the opportunity to use a range of applications geared towards providing increased efficiency and profitability, such as a management system, centralised pricing and promotional information, supplier management capabilities, etc.
[0162] Electronic Bill Presentment and Payment:
[0163] Electronic Bill Presentment and Payment (eBPP) is a flexible web-based application which digitises the current paper based billing, payment and notification process. The main functionality enables the creation and delivery of richly formatted bills, statements or notices, and associated advertising in an electronic format. This is transmitted via the electronic marketplace solution, to Retailers, and the return payment and remittance information to the biller.
[0164] Development software:
[0165] A software component of the business exchange is developed from the development software. This solution is made up of a number of integrated modules:
[0166] Customer Management—The Customer Management (CM) module provides users with a consistent user interface, via a single web site, to manage all interactions.
[0167] Order Management—The Order Management (OM) module provides all the necessary functionalities needed for an order management system deployed in a marketplace environment. The OM provides all the necessary work flow activities associated with an order including continuous tracking of customer orders, splitting them into individual supplier specific Purchase Orders (POs) and generating Invoices against the POs.
[0168] eBusiness framework—The eBusiness framework provides a set of workflows, guidelines and rules.
[0169] Demand Fulfilment—The Demand Fulfilment (DF) module is an intelligent order-fulfilment solution, addressing the total spectrum of needs in the order-promising process.
[0170] Fulfilment server—The Fulfilment server provides collaborative order fulfilment across discrete enterprises' individual supply chains, and an interface for integrating the front-end customer applications with back-end supply chain modules.
[0171] Business Intelligence—The Business Intelligence (BI) module provides the User Interface for interacting with the management information repository.
[0172] Data Flow:
[0173] The present invention can provide Retailers and Suppliers with significant supply chain benefits in areas including product, price and promotion visibility, a state-of-the-art POS and scanning solution, electronic order placement and processing and electronic bill presentment and payment.
[0174] Equipment Configuration:
[0175] Whilst the larger Convenience Organised Retailers may have the required technology to utilise the functionality of the present invention, ie. POS system and scanners, smaller independent Retailers may not have the necessary equipment.
[0176] The key equipment required by Convenience Retailers, in order to achieve certain benefits from the present invention, are scanners, PC's and connectivity to the Internet. It is also envisaged that further embodiments can provide additional functionality, such as the integration of EFTPOS card readers into the POS systems. Convenience stores may utilise existing infrastructure, requiring only connectivity to a computer network.
[0177] Further Examples
[0178] The following examples provide a more detailed outline of one embodiment of the present invention. These examples are intended to be merely illustrative and not limiting of the scope of the present invention. These examples describe “Use Case Specifications” which illustrate features of the main components or procedures of the exemplified embodiment(s). The following examples are to be read in conjunction with the FIGS.
[0179] Use Case Specification: <Transmit Data>
[0180] 1. Use Case Diagrams
[0181] Catalogue Maintenance: Master Catalogue and Associated Views
[0182] Catalogue Maintenance: Maintain Promotions
[0183] Catalogue Maintenance: Maintain Pricing
[0184] 2. Use Case Actors
[0185] Supplier ERP
[0186] Electronic Marketplace Solution Catalogue Staging Area
[0187] Buyer
[0188] POS/BOS
[0189] 3. Brief Description
[0190] In this use case, data is transferred from the supplier to Electronic Marketplace Solution, from the buyer to Electronic Marketplace Solution
[0191] Supplier ERP provides the following data: supplier catalogue data, user profile data, pricing data, supplier translation tables, and promotions data
[0192] The buyer from CO provides translation tables data
[0193] The supplier provides new products data, if retailer is part of the, Electronic Marketplace Solution POS/BOS installed base—data transmission is done from Electronic Marketplace Solution catalogue to the POS/BOS system using an interface
[0194] The independent retailer with their own POS/BOS system will choose the one of the two options
[0195] 4. Flow of Events
[0196] Basic Flow
[0197] Supplier transmits data in predefined format
[0198] Electronic Marketplace Solution catalogue administrator will down load the data file into the dump files in Electronic Marketplace Solution staging area
[0199] Electronic Marketplace Solution catalogue administrator sends acknowledgement after data is verified and loaded to Electronic Marketplace Solution catalogue
[0200] 4.2 Alternative Flow(s)
[0201] Electronic Marketplace Solution catalogue administrator is not successful in down loading data files
[0202] Electronic Marketplace Solution catalogue administrator should contact the supplier/buyer to confirm data file format, and request resending the data files
[0203] Electronic Marketplace Solution catalogue administrator transmits product update data to POS/BOS
[0204] No longer valid, Electronic Marketplace Solution will not update retailer's POS/BOS. The retailer will have to update POS/BOS before trying to add or order an item in Electronic Marketplace Solution
[0205] Buyer's saved list is updated in Customer Management (CM)
[0206] Electronic Marketplace Solution catalogue administrator sends notification message to buyer
[0207] Electronic Marketplace Solution catalogue administrator will generate buyer specific product update files
[0208] Electronic Marketplace Solution catalogue administrator transmits this data to the buyer
[0209] Buyer updates POS/BOS system
[0210] Data transmission between Electronic Marketplace Solution and Electronic Marketplace Solution Managed POS/BOS
[0211] Retailer initiates a POS/BOS session
[0212] POS/BOS product master file is updated based on feed from the Electronic Marketplace Solution catalogue
[0213] POS/BOS product master file is now synchronised with the retailers list/cart in the Electronic Marketplace Solution CM
[0214] Data transmission between Electronic Marketplace Solution and CO POS/BOS
[0215] CO POS/BOS is updated
[0216] CO transmits translation table data for Supplier ID's/Product Information
[0217] CO/Electronic Marketplace Solution systems administrator updates translation tables
[0218] Data transmission between Electronic Marketplace Solution and small retailers with independent POS/BOS systems
[0219] This group will have to choose between the data transmission flow for Electronic Marketplace Solution Managed POS/BOS, or CI POS/BOS
[0220] 5. Special Requirements
[0221] Release 1
[0222] Electronic Marketplace Solution Catalogue Staging area has to be developed to receive the supplier/buyer data (directory structure for pilot)
[0223] Data needs to be formatted based on Electronic Marketplace Solution's predefined standard
[0224] Data transmission medium should be fast and secure, to ensure that data transmitted is not corrupted
[0225] Basic scripts to automate the process of generating data files within Electronic Marketplace Solution
[0226] Transmission protocol has to be established with the supplier/buyer, if Electronic Marketplace Solution receives/sends data files via FTP
[0227] Basic scripts to validate add/update/delete data
[0228] Release 3
[0229] Scripts to automate the process of generating data files within Electronic Marketplace Solution
[0230] Scripts to validate add/update/delete data
[0231] Multi-enterprise catalogue functionality
[0232] Develop download button for buyers to generate a flat file that contains data on new items. This will save the Electronic Marketplace Solution catalogue administrator from having to generate and send data files to buyer to update POS/BOS. (no longer necessary because Electronic Marketplace Solution will not be responsible for updating POS/BOS system with new product information)
[0233] Phase 1
[0234] Develop interface between Electronic Marketplace Solution catalogue in CM and the Electronic Marketplace Solution managed POS/BOS system to synchronise the product master file and the Electronic Marketplace Solution catalogue
[0235] Develop translation tables between CI supplier/product data in the Electronic Marketplace Solution system, and the associated scripts to maintain/verify/load data
[0236] 6. Pre-Conditions
[0237] Supplier/buyer/Electronic Marketplace Solution catalogue administrator has generated flat file. For example: product, user profile, pricing, and promotion data
[0238] Electronic Marketplace Solution catalogue staging area has been set up with the required tables and associated attributes
[0239] Data load, extraction, and verification scripts have been developed
[0240] Electronic Marketplace Solution data formats have been established
[0241] 7. Post-Conditions
[0242] Data has been down loaded to the dump files in the Electronic Marketplace Solution catalogue staging area
[0243] Electronic Marketplace Solution catalogue administrator has sent acknowledgement to the supplier/buyer after successful down load, verification, and load into CM
[0244] 8. Data Requirements
[0245] User profile attributes. Still to be defined
[0246] Product Data
[0247] Supplier SKU Number
[0248] APN Number
[0249] Description
[0250] Short Description
[0251] Base UOM
[0252] Buy UOM
[0253] Packaging Information
[0254] Effectivity Dates (For New Products)
[0255] Flag (New, Update, Delete)
[0256] Product obsolete flag
[0257] Promotion Data
[0258] APN Number
[0259] Supplier SKU Number
[0260] Promotion Effectivity Date (To-From)
[0261] Discount
[0262] Min Order Qty
[0263] Max Order Qty
[0264] Promotion Details
[0265] Pricing
[0266] Supplier ED
[0267] Customer ID
[0268] APN Number
[0269] Nett Price
[0270] Field to identify add/update/delete
[0271] 9. Interfaces
[0272] Supplier/buyer will transmit the data based on their schedule. Based on the infrastructure the data file could be transmitted using FTP, e-mail attachment, or using an interface with the supplier's ERP system or the buyer's BOS/POS. The frequency of the data transmission will be done on a nightly batch process
[0273] Develop interface between Electronic Marketplace Solution catalogue in CM and the Electronic Marketplace Solution managed POS/BOS system to synchronise the product master file and the Electronic Marketplace Solution catalogue
[0274] Use Case Specification: <Update Lists>
[0275] 1. Use Case Diagrams
[0276] Catalogue Maintenance: Master Catalogue and Associated Views
[0277] 2. Use Case Actors
[0278] Customer Management
[0279] Electronic Marketplace Solution Catalogue Administrator
[0280] 3. Brief Description
[0281] Once the supplier catalogue has been updated with the new products and/or promotions, and the supplier has provided the data on the general/specific user profile they would like to push their new products and/or promotions. The Customer Management Suite should update the buyer's saved lists.
[0282] For an existing item on a retailer list, if it is on promotion then the price for that item should be updated
[0283] For promotional sku's generated by the supplier, since they do not exist on the retailer list will not be pushed but will be added to the hot deals page
[0284] 4. Flow of Events
[0285] 4.1 Basic Flow
[0286] Supplier sends the product, promotions, and user profile data
[0287] Electronic Marketplace Solution Catalogue Administrator loads the data to the supplier catalogue, in the respective category, i.e. new products in the new products category, and the promotions in the promotions category
[0288] The Electronic Marketplace Solution catalogue administrator during the load data process would have automated the process to push items to the respective buyer's list by updating the users profiles
[0289] Electronic Marketplace Solution catalogue administrator generates new products or new promotions alert
[0290] The buyer logs in and views the alert with regards to the new products/promotions based on profile
[0291] Buyers, based on user profile, access saved lists and add/delete items
[0292] 4.2 Alternative Flow(s)
[0293] Buyer does not have correct access to view new products/promotions
[0294] Either the user profile for the buyer has not been updated to reflect the correct access for those items, in which case the catalogue administrator should be able update their profile
[0295] 5. Special Requirements
[0296] Release 1
[0297] Semi-automated alerts should be generated to notify buyers about new/promotions products
[0298] User should have the ability to add new products to their lists from the Electronic Marketplace Solution website
[0299] Automatically delete catalogue items once the end date passes. Item will be deleted from saved lists/carts if no longer on master catalogue file
[0300] Semi-automated process by which items are pushed to the retailer list/cart
[0301] Release 3
[0302] New/Promotional products should be highlighted (high priority, release 3)
[0303] Alerts should be automatically generated to notify the buyers about new/promotional products
[0304] The respective shopping lists should be updated automatically based on the user profile provided by the supplier.
[0305] Promotion item is pushed to buyer's saved lists/carts if the item is already on the list at regular price. There are issues surrounding the “how” because promotions are often based on effective dates.
[0306] Scripts to automate process of updating lists
[0307] Multi-enterprise catalogue functionality
[0308] Phase 1
[0309] Develop interface between Electronic Marketplace Solution catalogue and the Electronic Marketplace Solution managed POS/BOS system to synchronise the product master file in POS/BOS with the retailers saved list/cart in CM
[0310] Develop translation tables to synchronise the product master file in CO POS/BOS with their saved list/carts in CM. Update data file will be transmitted to the system administrator at the CO POS/BOS, and they have the option to accept/reject those changes
[0311] 6. Pre-Conditions
[0312] Supplier data on new/promotional products has been successfully loaded into the catalogue
[0313] User profiles have been updated to reflect their ability to access/add these products to their lists
[0314] 7. Post-Conditions
[0315] Buyers have updated lists.
[0316] 8. Data Requirements
[0317] User profile data
[0318] New product catalogue data
[0319] Promotion data
[0320] 9. Interfaces
[0321] Develop interface between Electronic Marketplace Solution catalogue and the Electronic Marketplace Solution managed POS/BOS system to synchronise the product master file in POS/BOS with the retailers saved list/cart in CM
[0322] Develop translation tables to synchronise the product master file in CO POS/BOS with their saved list/carts in CM
[0323] Use Case Specification: <Load/Maintain Data>
[0324] 1. Use Case Diagrams
[0325] Catalogue Maintenance: Master Catalogue and Associated Views
[0326] Catalogue Maintenance: Maintain Promotions
[0327] Catalogue Maintenance: Maintain Pricing
[0328] 2. Use Case Actors
[0329] Customer Management
[0330] Electronic Marketplace Solution Staging Area
[0331] Buyer
[0332] 3. Brief Description
[0333] This use case describes the process of loading/maintaining in the CM. After data is verified, Electronic Marketplace Solution catalogue administrator will load the data from the Electronic Marketplace Solution catalogue staging area into the CM system. This process could be used to load the supplier catalogue data, user saved list data, user profile data, pricing data, promotion data, supplier/buyer translation table data.
[0334] 4. Flow of Events
[0335] Basic Flow
[0336] The Electronic Marketplace Solution catalogue administrator has run the verification script
[0337] The Electronic Marketplace Solution catalogue administrator starts the script to load the data from the Electronic Marketplace Solution staging area to the CM suite
[0338] When the load run is complete, the Electronic Marketplace Solution catalogue administrator reviews the log file to validate the number of records loaded, and the number of records that were rejected
[0339] The different data streams get loaded to their respective tables, i.e. price cube, supplier's catalogue, promotion summary page, and the translation tables
[0340] An exception report is generated indicating records that were not loaded and the reason for the record failure
[0341] The basic flow applies to the following:
[0342] Product data into supplier catalogues (updates, new products, promotions)
[0343] Price cube
[0344] Promotion summary page
[0345] Supplier/Buyer translation tables
[0346] Alternative Flow(s)
[0347] The Customer Management is unable load the file
[0348] Error message should be transmitted to Electronic Marketplace Solution catalogue administrator
[0349] Electronic Marketplace Solution catalogue administrator should review file and resolve issue
[0350] Electronic Marketplace Solution catalogue administrator reloads data
[0351] The buyer sends file of new items, entered in POS/BOS
[0352] Buyer has added a new item to their POS/BOS system
[0353] Buyer transmits file containing new items added to their POS/BOS system
[0354] Buyer notifies Electronic Marketplace Solution administrator of pending data transfer
[0355] Electronic Marketplace Solution administrator runs script to load data into buyer's specific list, only if the item is part of the Electronic Marketplace Solution catalogue
[0356] An exception report is generated indicating records that were not loaded and the reason for the record failure
[0357] Updating buyer profiles
[0358] The Electronic Marketplace Solution catalogue administrator has updated the supplier catalogue (product updates, new items, promotion items)
[0359] The Electronic Marketplace Solution catalogue administrator will the run the script to update the buyer profile based on the supplier criteria
[0360] The buyers profile is updated and their saved lists now show the new/promotion products the supplier is targeting at them
[0361] POS/BOS passes suggested order list to Electronic Marketplace Solution
[0362] POS/BOS generates list
[0363] Electronic Marketplace Solution systems generate a PO for suppliers in Electronic Marketplace Solution catalogue
[0364] Electronic Marketplace Solution person manually orders items from suppliers that are not in Electronic Marketplace Solution catalogue (note: for pilot only)
[0365] 5. Special Requirements
[0366] Release 1
[0367] Electronic Marketplace Solution staging area will need to be developed. Directory structure for release 1
[0368] Enable products based on start and end dates. Develop product effectivity date functionality, this will allow products to be viewed between their start and end dates
[0369] Data should be loaded in a batch process, and not one item at a time
[0370] Basic script to generate error file for exception handling
[0371] Basic scripts to load data to catalogue (basic scripts, semi-automated)
[0372] Scripts to update translation tables (basic scripts, semi-automated for pilot)
[0373] Develop the custom price cube, and the scripts to load the data (we will need to develop the data model)
[0374] Release 3
[0375] Multi-enterprise catalogue functionality
[0376] Staging area to verify data and begin load to CM.
[0377] When loading supplier catalogue data, the new products or promotions should be pushed to the buyer's saved lists based on user profile information. This process has to be automated (multi-enterprise catalogue functionality) (Manual process for pilot)
[0378] Automate the process to load data into CM tables
[0379] Seamless process
[0380] Script to generate error file for exception handling when loading the data. This script should incorporate intelligence indicating what caused the data to be rejected or why certain records failed
[0381] Error message should be sent to Electronic Marketplace Solution catalogue manager when data cannot be loaded. The message should include error codes.
[0382] Scripts to load data in supplier catalogue, buyer specific list, etc., based on user profile Scripts to enable maintaining user profiles to automate the push of items
[0383] Scripts to update translation tables
[0384] Phase 1
[0385] To maintain the data in the retailers POS/BOS system that is managed by Electronic Marketplace Solution, an interface will be developed to synchronize the product master file and the Electronic Marketplace Solution catalogue. Thus when a retailer adds a product to their saved list/cart in CM, the change will be replicated to the POS/BOS via this interface
[0386] To maintain the data in the CO POS/BOS system, when an item is added/updated to their list/cart in CM, the CO administrator will have to add that item into their POS/130S before it can be ordered, since their system has precedence over the list/cart in CM. Once they have added an item to their POS/BOS, they will have to send the translation tables data so as to synchronize these two data files. The HOS for CO has the prerogative to accept/reject list/cart updates data
[0387] No maintenance will be performed for retailers who have independent POS/BOS, they will have to choose between the above two options
[0388] Retailers with no POS/BOS, and who do not have Electronic Marketplace Solution maintained POS/BOS system, there will be no data loads, since they will procure directly from the web interface
[0389] 6. Pre-Conditions
[0390] Data is in the correct format to be loaded into CM
[0391] Data has been verified and we have a clean set of data
[0392] Data resides in Electronic Marketplace Solution Catalogue Staging Area
[0393] Develop translation tables for Electronic Marketplace Solution and CO supplier/product data. If we enforce the rule that they provide us EAN product numbers along with the respective supplier id's, we would then have to only maintain translation tables for the supplier id's assigned by the CO POS/BOS system and the Electronic Marketplace Solution assigned supplier id's
[0394] 7. Post-Conditions
[0395] Supplier Data has been updated in Customer Management System
[0396] Buyer saved lists have been updated
[0397] Retailer profiles have been updated
[0398] Supplier/Buyer translation tables have been updated
[0399] Price cube has been updated
[0400] 8. Data Requirements
[0401] Supplier Catalogue—Product data attributes
[0402] Pricing—Supplier ID, Product ID, Customer ID, Nett Price
[0403] User Profile—attributes to be defined
[0404] Promotion's summary page—attributes
[0405] Supplier/Buyer translation table data requirements
[0406] BOS/POS data attribute
[0407] Product effective dates
[0408] 9. Interfaces
[0409] The process by which data is loaded into the system will be via a batch job; the frequency of this load will depend on when suppliers/buyers send Electronic Marketplace Solution updates
[0410] Develop interface with POS/BOS for loading suggested order
[0411] Develop interface between Electronic Marketplace Solution catalogue in CM and the Electronic Marketplace Solution managed POS/BOS system to synchronize the product master file and the Electronic Marketplace Solution catalogue.
[0412] Use Case Specification: <Maintain Electronic Marketplace Solution/Supplier/Buyer Translation Tables>
[0413] 1. Use Case Diagrams
[0414] Catalogue Maintenance: Master Catalogue and Associated Views
[0415] 2. Use Case Actors
[0416] Electronic Marketplace Solution Catalogue Administrator
[0417] Customer Management
[0418] 3. Brief Description
[0419] Translation tables need to be maintained to map the different unique identifiers in the back office systems of the supplier, buyer, and Electronic Marketplace Solution. The following tables need to be maintained:
[0420] Supplier SKU—APN Number
[0421] Buyer SKU—APN Number, Buyer TUN Number
[0422] Electronic Marketplace Solution SKU—APN Number
[0423] APN Number
[0424] Supplier maintained Customer ID's—Electronic Marketplace Solution maintained Customer ID's
[0425] Buyer maintained Supplier ID's—Electronic Marketplace Solution maintained Supplier ID's
[0426] 4. Flow of Events
[0427] 4.1 Basic Flow
[0428] Electronic Marketplace Solution Catalogue Administrator requests data from each entity in the trading exchange
[0429] Electronic Marketplace Solution Catalogue Administrator loads data into the appropriate table
[0430] When an entity, for example the supplier adds a new item or maintains an existing item in their ERP, they provide Electronic Marketplace Solution with their SKU Number and the corresponding APN number in a flat file
[0431] Electronic Marketplace Solution Catalogue Administrator adds/updates the translation table in CM, if it is a new item Electronic Marketplace Solution will assign an internal identifier
[0432] 4.2 Alternative Flow(s)
[0433] Supplier adds/maintains customer in their ERP
[0434] Buyer adds/maintains item in their POS/BOS
[0435] Supplier adds/maintains an item
[0436] Buyer adds/maintains supplier in their POS/BOS
[0437] The Electronic Marketplace Solution catalogue administrator will follow the steps of the basic flow outlined above, but a different translation table will be updated depending on the action performed
[0438] Electronic Marketplace Solution—Electronic Marketplace Solution maintained POS/BOS system
[0439] For those retailers that have Electronic Marketplace Solution maintained POS/BOS systems, we will establish the rules for how the product, and supplier information is maintained, this will to eliminate the need for translation tables, as products in the POS/BOS system will be assigned the EAN number, and the supplier of that product will be assigned the quarto supplier number in the POS/BOS
[0440] Electronic Marketplace Solution product information—Supplier Product information
[0441] The rule has to be established that when a supplier sends us their product information, the EAN number along with the Electronic Marketplace Solution assigned id for that supplier is part of the product data file. The EAN number along with the Electronic Marketplace Solution assigned supplier id will be the unique identifier for that item, this is because a product can be procured from multiple suppliers
[0442] Electronic Marketplace Solution product information—CO POS/BOS systems
[0443] A. For those CO POS/BOS systems that store EAN numbers, we would not need translation tables for the products since this is the industry standard, and in the Electronic Marketplace Solution catalogue we are storing the products per EAN numbers
[0444] B. For those CO POS/BOS systems that do not store EAN numbers, we would have to maintain translation tables between their SKU and the EAN in Electronic Marketplace Solution
[0445] C. For the supplier id's stored in the product master file of the CO POS/BOS system, we would have to maintain translation tables
[0446] 5. Special Requirements
[0447] Release 1
[0448] Business rules that govern the maintaining of these translation tables (data format, time, frequency)
[0449] Basic scripts to load/verify data
[0450] Translations tables will need to be custom built in the CM suite. High priority, must be in release 1 of pilot, Medium level of work
[0451] Release 2
[0452] Scripts to load/verify data into translation tables. Low priority, high level of work. Needs to be automated for release 3
[0453] Multi-enterprise catalogue functionality (note: Supplier and customer ID will still have to be maintained even after the multi-enterprise catalogue roll out for release 3)
[0454] Electronic Marketplace Solution—Electronic Marketplace Solution maintained POS/BOS system
[0455] For those retailers that have Electronic Marketplace Solution maintained POS/BOS systems, we will establish the rules for how the product, and supplier information is maintained, this will eliminate the need for translation tables, as products in the POS/BOS system will be assigned the EAN number, and the supplier of that product will be assigned the quarto supplier number in the POS/BOS
[0456] Electronic Marketplace Solution product information—Supplier Product information
[0457] The rule has to be established that when a supplier sends us their product information, the EAN number along with the Electronic Marketplace Solution assigned id for that supplier is part of the product data file. The EAN number along with the Electronic Marketplace Solution assigned supplier id will be the unique identifier for that item, this is because a product can be procured from multiple suppliers
[0458] Phase 1
[0459] Electronic Marketplace Solution product information—CO POS/BOS systems
[0460] A. For those CO POS/BOS systems that store EAN numbers, we would not need translation tables for the products since this is the industry standard, and in the Electronic Marketplace Solution catalogue we are storing the products per EAN numbers
[0461] B. For those CO POS/BOS systems that do not store EAN numbers, we would have to maintain translation tables between their SKU and the EAN in Electronic Marketplace Solution
[0462] C. For the supplier id's stored in the product master file of the CO POS/BOS system, we would have to maintain translation tables
[0463] 6. Pre-Conditions
[0464] Each entity can provide the specified information
[0465] Translation tables have been set-up in customer management
[0466] Interface has been established to update translation tables between modules of
[0467] 7. Post-Conditions
[0468] Translation tables are in synch with the different back office systems
[0469] 8. Data Requirements
[0470] APN Number
[0471] Supplier maintained Customer ID's
[0472] Electronic Marketplace Solution maintained Customer ID's
[0473] Buyer maintained Supplier ID's
[0474] Electronic Marketplace Solution maintained Supplier ID's
[0475] Supplier SKU Number
[0476] Buyer SKU Number
[0477] Electronic Marketplace Solution assigned internal number
[0478] Buyer TUN Number
[0479] 9. Interfaces
[0480] POS/BOS to Electronic Marketplace Solution
[0481] Electronic Marketplace Solution to supplier
[0482] Between modules of
[0483] Use Case Specification: <Generate Message>
[0484] 1. Use Case Diagrams
[0485] Catalogue Maintenance: Master Catalogue and Associated Views
[0486] 2. Use Case Actors
[0487] Electronic Marketplace Solution Catalogue Administrator
[0488] Customer Management
[0489] 3. Brief Description
[0490] This use case describes the process of generating and sending the “Alert” message to inform users when Electronic Marketplace Solution receives new supplier data (new products or promotions). CM will generate an “Alert” message that the user will see on the Electronic Marketplace Solution screen. This message will inform the user that new products/promotions are available.
[0491] 4. Flow of Events
[0492] 4.1 Basic Flow
[0493] A supplier catalogue has been updated with new products and promotional products
[0494] CM determines which users should see which products based on user profile information
[0495] CM generates “Alert” message to inform users about the new supplier data
[0496] CM sends (or posts) the “Alert” message to the appropriate user's Electronic Marketplace Solution website
[0497] 4.2 Alternative Flow(s)
[0498] The “Alert” message is not generated
[0499] The “Alert” message is not generated even though there is new supplier information that matches various user profiles
[0500] Electronic Marketplace Solution catalogue administrator should monitor the process to ensure that messages are created and sent
[0501] 5. Special Requirements
[0502] 5.1 Release 1
[0503] Semi-automated process to generate alerts and send them to buyers, this function will be performed by the catalogue administrator
[0504] 5.2 Release 3
[0505] Button in the “Alert” message that will take the user directly to the list of new products or hot deals (low priority, release 3)
[0506] “Alert” messages automatically generated and sent to users based on the user profile. Note: Automating this process would be simple for a general message to all users, but very difficult to customize, based on user characteristics.
[0507] 6. Pre-Conditions
[0508] Supplier has submitted new product data or promotions data
[0509] Electronic Marketplace Solution catalogue administrator was able to load new data in Electronic Marketplace Solution catalogue
[0510] User profile gives access to user to view new products and promotions
[0511] New products/promotions summary page has been set up
[0512] User profiles have been updated
[0513] Saved lists have been updated
[0514] 7. Post-Conditions
[0515] User receives “Alert” message informing them of new products or promotions
[0516] 8. Data Requirements
[0517] Product attributes
[0518] User profile attributes
[0519] Pricing attributes
[0520] Promotion attributes
[0521] Message Details
[0522] 9. Interfaces
[0523] Use Case Specification: <Generate Frequently Ordered List>
[0524] 1. Use Case Diagrams
[0525] Catalogue Maintenance: Maintain Frequently Ordered List
[0526] 2. Use Case Actors
[0527] Buyer
[0528] Order Management Suite or POS
[0529] 3. Brief Description
[0530] This use case describes the vision of generating a frequently ordered list based on PO history. This list would include frequently ordered products and quantities. The PO history would be extracted from Electronic Marketplace Solution or from the retailer's POS/BOS. The frequently ordered list could be generated by clicking on a button in the Electronic Marketplace Solution website. PO history is analyzed and the frequently ordered list is generated. The buyer can review the list, modify the list, and/or make the list into an order.
[0531] 4. Flow of Events
[0532] 4.1 Basic Flow
[0533] Buyer initiates new session
[0534] Buyer decides to generate a frequently ordered list
[0535] Buyer click on button to generate list based on PO history
[0536] CM accesses PO history to generate the frequently ordered list
[0537] List is displayed in web user interface
[0538] Buyer reviews list
[0539] Buyer may modify list, save list, and/or make the list into an order
[0540] 4.2 Alternative Flow(s)
[0541] Buyer would like to delete an item from the Frequently Ordered List
[0542] Buyer opens his saved frequently ordered list
[0543] Buyer selects item to delete
[0544] Buyer clicks on “Delete Item” button
[0545] CM removes item from buyer's frequently ordered list
[0546] CM save changes to frequently ordered list
[0547] 5. Special Requirements
[0548] 1. Release 1
[0549] User will manually update the frequently ordered list for pilot. With in CM a use can develop different saved carts that are essentially their frequently ordered list. Work around: It may be possible to treat the Frequently Ordered List similar to the suggested order list. The buyer would than be able to make the frequently ordered list an order or keep it as a saved cart
[0550] The Buyer should be able to modify the frequently ordered list
[0551] The Buyer should be able to save the cart and access it in the future
[0552] Buyer should be able to make the frequently ordered list into an order
[0553] 2. Release 3
[0554] Generate the frequently ordered list, based on PO history that is stored in either POS/BOS or in the order management system in Electronic Marketplace Solution. To automate this process we would have to build custom scripts based on some rules that would look at the different PO's and then generate the list
[0555] 6. Pre-Conditions
[0556] Buyer initiates new session
[0557] Supplier catalogue has been maintained
[0558] User profiles have been set-up
[0559] There is PO history available to generate the frequently ordered list
[0560] A button has been created that will generate a frequently ordered list based on PO history when a buyer clicks on it
[0561] Business rules to generate the frequently ordered list have been established and maintained
[0562] 7. Post-Conditions
[0563] Buyer has created a frequently ordered list
[0564] Buyer can view the frequently ordered list
[0565] Buyer can added an item to the frequently ordered list
[0566] Buyer can deleted an item on the frequently ordered list
[0567] Buyer can change a quantity on the frequently ordered list
[0568] Buyer can save the frequently ordered list
[0569] 8. Data Requirements
[0570] Catalogue data requirements
[0571] PO history from Electronic Marketplace Solution or POS/BOS
[0572] Business rules for generating and maintaining frequently ordered list
[0573] User profile requirements
[0574] 9. Interfaces
[0575] If frequently ordered list is generated based on PO history from retailer's POS/BOS, CM would need to interface with POS/BOS.
[0576] Use Case Specification: <Verify Data>
[0577] 1. Use Case Diagrams
[0578] Catalogue Maintenance: Master Catalogue and associated Views
[0579] Catalogue Maintenance: Maintain Promotions
[0580] Catalogue Maintenance: Maintain Pricing
[0581] 2. Use Case Actors
[0582] Electronic Marketplace Solution Catalogue Administrator
[0583] Electronic Marketplace Solution Catalogue Staging Area
[0584] 3. Brief Description
[0585] In this use case the Electronic Marketplace Solution catalogue administrator starts the verification scripts to ensure that the supplier/retailer data has been formatted to the Electronic Marketplace Solution standard. The scripts should ensure that referential integrity is maintained. The Electronic Marketplace Solution catalogue administrator will generate a list of those records that fail. The output of this step is to have clean data before loading CM suite.
[0586] 4. Flow of Events
[0587] 4.1 Basic Flow
[0588] Electronic Marketplace Solution catalogue administrator has loaded data files into the dump tables in Electronic Marketplace Solution catalogue staging area
[0589] Electronic Marketplace Solution catalogue administrator runs the data verification script on the supplier/retailer provided data
[0590] On successful completion of the script, data is ready to be loaded into CM
[0591] 4.2 Alternative Flow(s)
[0592] Verification script generates invalid data
[0593] Electronic Marketplace Solution catalogue administrator reviews data file to resolve issues
[0594] If issues are successfully resolved, data is ready to be loaded to CM suite
[0595] If issues are not resolved, Electronic Marketplace Solution catalogue administrator should run script to generate exception report
[0596] Electronic Marketplace Solution catalogue administrator should send exception report to appropriate supplier/retailer for resolution
[0597] 5. Special Requirements
[0598] 1. Release 1
[0599] Electronic Marketplace Solution has defined the different data format and integrity rules around the different reference tables, such as UOM, Category, etc.
[0600] Generate exception report scripts
[0601] Basic data verification scripts
[0602] Staging area to test data before data is loaded CM suite. (Use directory structure for pilot). Basic scripts for loading, verifying, and generating exception reports
[0603] 1. Release 3
[0604] Data verification scripts, with intelligence built into the error report detailing the reason the record failed
[0605] Multi-enterprise catalogue development
[0606] 6. Pre-Conditions
[0607] Data verification scripts have been developed
[0608] Electronic Marketplace Solution Staging Area has been set-up
[0609] Suppliers/retailers have provided files in Electronic Marketplace Solution format, and they have developed the required data extraction scripts
[0610] Script to generate exception report
[0611] Data file from the supplier/retailer has been down loaded to the Electronic Marketplace Solution staging area
[0612] Error Codes have been defined
[0613] 7. Post-Conditions
[0614] Data file has been verified, and records have been marked as accept, or reject
[0615] Exception list has been generated, and is ready to be transmitted to the supplier/retailer for resolution (if the Electronic Marketplace Solution Catalogue Administrator cannot resolve the issues)
[0616] 8. Data Requirements
[0617] Product attributes
[0618] Customer profile attributes
[0619] Pricing attributes
[0620] Promotion attributes
[0621] Error codes
[0622] Translation table data
[0623] 9. Interfaces
[0624] Use Case Specification: <Review/Resolve Exceptions>
[0625] 1. Use Case Diagrams
[0626] Catalogue Maintenance: Master Catalogue and Associated Views
[0627] Catalogue Maintenance: Maintain Pricing
[0628] Catalogue Maintenance: Maintain Promotions
[0629] 2. Use Case Actors
[0630] Electronic Marketplace Solution Catalogue Administrator
[0631] Electronic Marketplace Solution Catalogue Staging Area
[0632] Supplier ERP
[0633] Buyer
[0634] 3. Brief Description
[0635] In this use case the Electronic Marketplace Solution catalogue administrator will review the exception records that are generated once the verification scripts have been run, or for those records that were rejected during the data load process. The verification scripts will generate the list of all the records that do not match the Electronic Marketplace Solution catalogue data format. The scripts will also track those records that fail with the database integrity rules. The Electronic Marketplace Solution catalogue administrator reviews/resolves issues on exception report. If Electronic Marketplace Solution catalogue administrator is unable to correct records, the data will be sent back to the supplier/buyer for review and resolution.
[0636] 4. Flow of Events
[0637] 4.1 Basic Flow
[0638] Electronic Marketplace Solution catalogue administrator has performed either the verify data or data load process
[0639] Exception report for error records will be generated with error codes
[0640] Electronic Marketplace Solution catalogue administrator will review records, and resolve issues
[0641] If the issue can be resolved, the Electronic Marketplace Solution catalogue administrator loads data
[0642] 4.2 Alternative Flow(s)
[0643] Electronic Marketplace Solution Catalogue Administrator cannot resolve the exceptions
[0644] The Electronic Marketplace Solution Catalogue Administrator will send the exceptions list to the respective supplier or buyer for resolution
[0645] 5. Special Requirements
[0646] 1. Release 1
[0647] Exception reports should be in a format that is acceptable to the supplier/buyer, so they can resolve the errors quickly
[0648] Data should be loaded in a batch process, and not one item at a time
[0649] Basic scripts to verify data, load data, generate exception reports
[0650] Staging area to test and hold data. (Use directory structure for pilot)
[0651] 2. Release 3
[0652] Verification scripts with intelligence to list the attribute and the error (develop basic scripts for pilot, but intelligent error reporting will be needed for release 3)
[0653] Multi-enterprise catalogue functionality, thus the supplier will be responsible for maintaining their catalogue
[0654] 6. Pre-Conditions
[0655] Data verification scripts/data load has been run
[0656] Exception report has been generated
[0657] Error codes have been defined
[0658] 7. Post-Conditions
[0659] Electronic Marketplace Solution catalogue administrator resolves the exceptions and the data is ready to load
[0660] Supplier/buyer has received the exceptions list, and is in the process of resolving the issue
[0661] 8. Data Requirements
[0662] Product attributes
[0663] Pricing attributes
[0664] Promotion attributes
[0665] User Profile attributes
[0666] Buyer translation table
[0667] BOS/POS requirements
[0668] Saved list data requirements
[0669] The exception report should have an error code field
[0670] 9. Interfaces
[0671] We need to follow up on interface details. This is still unresolved.
[0672] Use Case Specification: <Review Promotions>
[0673] 1. Use Case Diagrams
[0674] Catalogue Search and Browse
[0675] 2. Use Case Actors
[0676] Supplier
[0677] HO Category Manager
[0678] Buyer
[0679] Site Staff
[0680] Site Staff
[0681] Customer Management
[0682] 3. Brief Description
[0683] This use case describes how users, based on their user profiles, will review promotions during search, browse, and order capture activities. The user should also be able to go directly to the list of items that are on promotion by selecting the promotions summary page. The user should be able to drill down on the item to view the promotion details, such as min/max order quantity, expiration date, special packaging, discounts etc
[0684] 4. Flow of Events
[0685] 4.1 Basic Flow
[0686] The user initiates their session
[0687] The user selects the promotions summary page
[0688] The user reviews the list of items on promotion
[0689] The user clicks on the view special details button
[0690] The user is then taken to the promotions template where they can review the details
[0691] The user then has the choice of going back to the promotions list, or adding the item to their shopping cart.
[0692] 4.2 Alternative Flow(s)
[0693] User is in the order capture process
[0694] The user is currently in the process of reviewing their order list
[0695] Those items on promotion will have an icon (for e.g. a star) to designate that they are on promotion. The user should be able to view the details on the promotion by clicking on the view special details button
[0696] The user is then taken to the promotions template, where they can either go back to the order list, or go to the edit order page to adjust the line item
[0697] User is in the process of searching for an item
[0698] The user is currently in the process of searching for an item. The user is presented with the result set
[0699] Those items on promotion win have an icon (for e.g. a star) to designate that they are on promotion. The user should then be able to view the details on the promotion by clicking on the view promotion details button
[0700] The user is then taken to the promotions template, where they can either go back to the search page, or select the item and add it to their shopping cart
[0701] 5. Special Requirements
[0702] 5.1 Release 1
[0703] Promotion details can be accessed by clicking on the item. This is a link to a static page that contains the promotion details (the description of the promotion)
[0704] To view the promotion details, the promotion description text will have to be rendered in some format. All the promotion details, such discounts, etc. will have to be part of the promotion description
[0705] Hot deals page. Static text page for pilot
[0706] If a price changes on an item so that it is considered on promotion, the APN should remain the same. If there is some other type of change, a new APN should be created
[0707] 5.2 Release 3
[0708] Promotions are displayed when the user is performing the following functions: Search, Browse, Order Capture
[0709] Promotions can be targeted to buyers that fit the profile defied by the supplier
[0710] Set up hot deals summary page to list items from all suppliers and show items by category, by product group, by line item. The catalogue will have to be modeled to accommodate this functionality
[0711] Automate the process by which the user profile is updated to grant/deny access to a promotional item
[0712] Automating the process by which promotional items are pushed to the buyer's lists based on the profile provided by the supplier (will accept workaround for pilot, workaround is sending an alert to user about new promotions, this issue will be easier to solve with Aspect functionality that should be available in for release 3). High Priority
[0713] Set up special indicator to designate an item is on promotion during search/browse/order capture (different color indicator is preferred by Electronic Marketplace Solution). High Priority
[0714] Promotions are displayed based on start and end dates, i.e. set up effective date functionality, this will drive when the item is available to be viewed
[0715] 5.3 Phase 1
[0716] Develop rules to match promotion restrictions such as min/max order amount, effective dates, etc. when the item is added to the shopping cart
[0717] Click count on hot deals summary page, advertising banners, etc.
[0718] Since generates a unique number for items on promotions, it will be difficult for the supplier/buyer to analysis data for reporting reasons. Workaround: Electronic Marketplace Solution maintains translation tables between the regular SKU number and the Promotional SKU number
[0719] 6. Pre-Conditions
[0720] Supplier's catalogues/lists/cart/promotions summary page have been set-up
[0721] User profiles have been set-up based on supplier target market data (i.e. profiles, specific retailers)
[0722] Promotional data has been set-up based on data provided by supplier details
[0723] Promotions summary page has been set up
[0724] 7. Post-Conditions
[0725] User has reviewed promotion details
[0726] User has selected an item to add to cart
[0727] User has selected items for comparison
[0728] 8. Data Requirements
[0729] Start/End Date
[0730] APN Number
[0731] Promotion Tag Line
[0732] Discount %
[0733] Promotion Description
[0734] Min Order Amount
[0735] Max Order Amount
[0736] Target Market Profile Data
[0737] Retailer ID
[0738] 9. Interfaces
[0739] Pricing cube has been set-up in Customer Management. This price cube contains pricing per supplier, per customer, per product. The pricing data load from the supplier ERP system should be a batch load process.
[0740] Use Case Specification: <Review/Add/Delete Available Item>
[0741] 1. Use Case Diagrams
[0742] Catalogue Maintenance: Maintain Company List
[0743] Catalogue Maintenance: Maintain Frequently Ordered List
[0744] Catalogue Maintenance: Maintain My List
[0745] Catalogue Maintenance: Maintain Promotions
[0746] 2. Use Case Actors
[0747] HO Category Manager (in detailed text below, the term “buyer” includes HO Category Manager)
[0748] Buyer
[0749] Theo
[0750] Customer Management
[0751] 3. Brief Description
[0752] This use case outlines how a buyer can add products to their saved lists or cart. The following options are available:
[0753] Buyer reviews products that are available based on user profile. Buyer adds items to a saved list/cart. For example, in a convenience organized setting the HO category manager would add products to the company list. The MSF store manager would add items to my list. For convenience independent, the store manger/owner would be able to update lists.
[0754] Buyer reviews new product lists and adds items to a saved list or cart
[0755] Buyer reviews hot deals page and adds items to a saved list or cart
[0756] 4. Flow of Events
[0757] 4.1 Basic Flow
[0758] Buyer reviews products available
[0759] Buyer reviews new product lists and promotions lists
[0760] Buyer finds products to add to one of their saved lists or cart
[0761] Buyer clicks on a button next to the item to add the item to a saved list or cart
[0762] CM saves the buyer's lists/carts
[0763] The buyer can access the lists/carts in the future
[0764] The user profile has to be maintained based on the supplier provided data to limit which items a buyer can access.
[0765] 4.2 Alternative Flow(s)
[0766] Buyer does not want to add any items to a saved list
[0767] Buyer reviews supplier catalogues, new product lists, and promotions
[0768] Buyer does not want to add any items to a saved list
[0769] Buyer should be able to exit product list without selecting items
[0770] Buyer should be able to access other Electronic Marketplace Solution screens
[0771] Buyer would like to delete items from saved lists or cart
[0772] Buyer reviews saved list or cart to modify
[0773] Buyer selects item to delete
[0774] Buyer clicks on “delete” item button
[0775] Item is removed from saved list or cart
[0776] The list/cart is saved
[0777] 5. Special Requirements
[0778] 1. Release 1
[0779] Button that enables buyer to add item to a list/cart
[0780] Button that enables buyer to delete item from list/cart
[0781] Current functionality is acceptable, with regards to add/delete of an item
[0782] Semi-Automated process to push items based on user profile. The catalogue administrator will have to perform this function
[0783] 2. Release 3
[0784] Button or Drop down box where buyer can choose which list to add the item
[0785] Automated push of new products and promotions based on user profile. Automated generation of alert message, informing users that there are new/promotion products available. (Semi-automated process for pilot. To determine the level of automated for release 3)
[0786] 6. Pre-Conditions
[0787] Buyer initiated new session
[0788] Buyer has the appropriate profile to view items
[0789] Supplier catalogue has been updated
[0790] User profile has been set up
[0791] 7. Post-Conditions
[0792] Item is added/deleted to one of the buyer's saved lists/cart
[0793] Buyer can access other screens in Electronic Marketplace Solution instead of adding an item to a saved list
[0794] After the buyer has added an item, they need to ensure that their respective POS/BOS system has also added the same item before it can be ordered through Electronic Marketplace Solution
[0795] 8. Data Requirements
[0796] User profile
[0797] Product information
[0798] Pricing information
[0799] Promotions information
[0800] 9. Interfaces
[0801] POS/BOS needs to be updated with new product information
[0802] Use Case Specification: <Notify Community of Changes/Adds/Deletes>
[0803] 1. Use Case Diagrams
[0804] Catalogue Maintenance: Maintain Company List
[0805] 2. Use Case Actors
[0806] HO Category Manager
[0807] Customer Management
[0808] 3. Brief Description
[0809] This use case describes how the HO would notify the user community about changes, adds, and deletes to the company list. For example, when new products are available for the buyer to order or add to a saved list.
[0810] 4. Flow of Events
[0811] 4.1 Basic Flow
[0812] Electronic Marketplace Solution catalogue administrator uses a semi-automated process to send out alerts. The alerts will be g