Back

Introduction to BFshop

The foundation, purpose, and overall direction behind BFshop as a full-stack AI-enhanced business system.

Introduction to BFshop


In this article I lay the groundworks for my BF shop project, focusing on its basic structure and purposes.


What is BFshop?


I'm currently building my first AI enhanced business system, BFshop.


BFShop is a business simulation that I'm using to explore how AI and automation can be integrated into real business systems, as well as build my first full stack system.


It is both purposeful and experimental.


The project is at its core an ecommerce store featuring the merchant and customer end for users to interact with. But the reality is more of a simulated production business; there will be workflows coordinated to streamline real processes; a customer service AI assistant, an AI assistant for the merchant and a shared database.


Rather than treating AI as a standalone feature, BFShop explores how AI, automation and software integrations can work together within a complete business system.


Why am I building it?


AI has moved faster than the world around it. We're playing catch up.


Businesses today rely on dozens of different platforms; websites, CRMs, email, accounting software, cloud storage, internal tools. More often than not, they're disconnected, leaving people to move information between them manually.


I'm interested in how AI fits into that ecosystem. Not as a novelty, but as one part of a connected business system alongside automation, integrations and the software people already use every day.


BFShop is my way of experimenting with that. I'm exploring how AI can work with full-stack applications, shared data, workflow automation and external platforms to reduce repetitive work and create systems that are genuinely useful to businesses of any size.


It's also my first full-stack software project, making it an opportunity to learn backend development, system architecture and infrastructure while building something with a real purpose.


Core components


Customer interface


This is the ecommerce store where customers would place orders, featuring a chatbot for querying product, orders and business information. Placed orders will go through the backend and write to the database. The bot will be helpful and easy to use, drawing on live data.


Merchant interface


Orders will be written here from the database via the shared backend in three panels: received, delivered, arrived.


This will also feature an AI chat interface which will act as an assistant to the merchant; This serves as an experiment into how AI may gradually shift business software from traditional click-based interfaces towards conversational ones.


Backend


The backend will consist of four layers:


  • Control layer
  • Application (app) layer
  • Service layer
  • Data layer

The control layer will contain API routes which accept requests and deliver responses to the frontends.

The application layer will decide the sequence of events for how to execute those requests.

The service layer will contain business rules and answer questions such as 'is this order valid' or 'what should the total be'. It prepares data and asks the data layer to read or write it.

The data layer will perform database operations such as creating, reading, updating and deleting records.


Automation and Integration


Modern systems are a web of interconnected platforms; Slack, Google Drive, Microsoft 365, CRMs, among others; BFshop will use n8n integrations to coordinate workflows for the purpose of reducing work for the merchant and keeping the customer informed.


AI Overwatch


One concern with AI technology as time goes on is in its autonomy; as AI systems become capable of carrying out work on behalf of users, visibility into their actions becomes increasingly important.


That's why I'm building the feature AI Overwatch, which will display the AI's actions and available capabilities in a transparent way.


Data


The system is built around a number of shared data entities.


  • Product; the product itself and its traits.
  • Order; the sum of the products placed by a user in the customer frontend.
  • OrderItem; an individual line within the Order data entity.
  • Customer; the customer logged in at a given time. This will only include one entry as authentication is one more element which would add complexity to an already complex project.
  • ActivityLog; this will store data taken from backend requests and allow visibility over AI behaviour, to be presented in AI overwatch.

Final Thoughts


BFshop is a full business simulation that will develop as time goes on; features may be added, existing ones altered.


Rather than treating BFshop as a finished specification, I'm seeing it as an evolving engineering project. As I learn more, the system will evolve more.


It should be noted that while this is a business simulation some parts may be left out; financial information, legal detail.