Skip to content

Instantly share code, notes, and snippets.

@igorevichnikitos5
Last active November 18, 2023 19:05
Show Gist options
  • Save igorevichnikitos5/0705c3fedbae27f49691191ecd171002 to your computer and use it in GitHub Desktop.
Save igorevichnikitos5/0705c3fedbae27f49691191ecd171002 to your computer and use it in GitHub Desktop.

Functional requirements

Pilot

Must haves

  • An interactive storefront for selling a displayed assortment of goods

    • Support for sensory, visual and audio interfaces at the hardware level.
    • Manual order generation by the customer on the virtual storefront in their native language. Supported languages: Chinese, English, Russian, Ukrainian, Thai, German, Spanish, Hebrew.
    • Highlighting of the selected goods in the cells of the interactive storefront.
    • Integration with a POS-system for the payment of goods.
    • Up to 40 items on a single showcase.
    • Tracking the balance of goods.
    • Automatic recording of the inflow of goods with confirmation by the operator.
    • Automatic autonomous transmission of information about sales, proceeds, equipment failures, exchange sessions with the POS system, history of communication with customers to the storefront management system.
  • Storefront management system (backoffice).

    • Storefront grouping.
      • Franchise = one or more retail outlets (at Pilot stage - one single franchise).
      • Retail outlet = one or more storefronts (at the Pilot phase - one single storefront).
    • Integration with the customer's merchandising system.

Final

Should Have:

  • Storefront autonomy at the level of manual product selection (sales should work without internet access).
  • Gateway of storefront integration with AI (initially - GPT4 Turbo).
    • Ability to maintain a conversation with the customer.
    • Voice and text recommendations with cart filling analysis (e.g., "this product is often purchased with...").
  • Network-wide analytics.
  • Customer authorization, loyalty program.
  • Flexible management of users and access rights to franchises and outlets.

Nice to have:

  • Flexible tool for customizing shopping scenarios at each outlet (e.g. delivery/pre-order).

Non-functional requirements

  • The allowed number of server software downtime is 1 hour (to be specified during pilot operation).
  • Kiosk downtime hours are not specified.

Glossary

Franchise - a group of outlets owned by one company or person Retail outlet - a store

Restrictions

  • Number of types of goods on the showcase at one time: <=40 items (no more)
  • Supported languages: Список заполнить
  • Initial integration is performed with POS system: loyverse.com.
  • In case of connectivity issues, all possible local scenarios should be executable.

General schemes of interaction with the product

Trading scheme

изображение

Data exchange scheme

изображение изображение

Stakeholders

Internal

  • Timofey
  • Grigory
  • Vadim

External

  • Hotel chain = first franchise
  • Investor who wants to turn it into a franchise
  • Equipment manufacturer

Time Restrictions

Pilot Version

  • Until the end of January
  • Integration with off-the-shelf merchandising and accounting system
  • Focus on maximizing the use of ready components

Final Version

  • Until the end of May
  • No POS system selected or no suitable POS system available

Operation

  • Project infrastructure and it's management will be handled by the Contractor and will be paid for by the Customer. Project infrastructure in this clause is represented by backoffice hosting servers. Budget - calculated according to the results of pilot operation.

  • Support structure:

    • First line - from the Customer's side. Operator, technician, programmer. Total budget: 3-4 thousand dollars
    • The second line - from the Contractor.
    • The order of support: the customer calls the operator - the operator passes the information to the technician or programmer - they either fix the problem themselves, or pass it to the second line.
  • Installation and mounting of kiosks (outlets), traffic and repairs are paid by the Customer.

Cost-benefit analysis

The project has not been fully developed on the Customer's side. Timothy and the Customer will hash out the details soon. To recoup, the project needs 3 sales per day per point.

Work plan

Month 1 (pilot)

  • Merchandise management system (adding a product item, editing, deleting)
  • Storefront management system (creating showcases, deleting showcases, making changes to the created showcases \number of goods, number of cells, etc.).
  • Basic integration with POS - order transfer

Month 2

  • User management system (creating users, granting rights, editing rights, deleting users)
  • Electronic assistant (AI-assistant)

Month 3

  • POS management system (merge storefronts into a point of sale, delete storefronts from a point of sale, assign a user to a point of sale, delete a user from a point of sale, make changes to the number of storefronts/users in a point of sale)
  • Voice assistant

Month 4

  • Deep integration with POS-system (with cash register)

Month 5

  • Analytics on the available data (showcases, their filling, sales outlets, their filling, users, users' activities)

Month 6

  • Franchise management system (creating, editing, deleting, adding outlets; assigning, creating, modifying and deleting users)

Planned architecture

изображение

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment