TR2025008339A2 - INTEGRATED SOCIAL-COMMERCIAL PLATFORM SYSTEM THAT OFFERS PHYSICAL ORDERING AND DELIVERY THROUGH SOCIAL MEDIA SHARING (STORY) - Google Patents

Abstract

It is about an integrated social-commercial platform system that enables the creation of product or service orders through social media posts (stories) and the physical receipt of these orders.

Description

DESCRIPTION INTEGRATED SOCIAL-COMMERCIAL PLATFORM SYSTEM PROVIDING PHYSICAL ORDERING AND DELIVERY THROUGH SOCIAL MEDIA SHARES (STORIES) Technical Field The invention relates to a technical field that brings together social media platforms, mobile applications, e-commerce systems, payment infrastructures, POS (Point of Sale) device integration, and the digitalization processes of local businesses. More specifically, the invention encompasses an integrated social-commercial platform system that allows users to order products/services for themselves and others via social media posts (stories) and to physically receive these orders; it also allows businesses to manage orders, menus, and promotional campaigns through a management panel. The invention falls within an innovative technological field that extends social media interactions into the physical world, combining user experience with individual and social consumption. State of the Art: Widely used social media platforms today (e.g., Instagram, TikTok, Facebook, etc.) allow users to share content in story format and interact with it. However, these platforms generally lack the ability to directly order through story sharing, order gifts, food, or various beverages for themselves or others, or receive physical delivery of the order. Even if users see a product or service they like in a story, they are often forced to order through a different platform or method. Current online ordering systems typically operate within their own closed ecosystems and do not offer direct integration with social media platforms. For example, Yemeksepeti, Getir, Uber Eats, etc. In these systems, orders are placed through the relevant application's own interface. Current systems fail to provide a story-based ordering experience enriched with instant social interactions. From a business perspective, current systems handle order and payment management using POS devices or manual control systems. Direct order flow and POS device integration with story-based payment management are not possible. Managing potential requests from social media directly within the order flow and POS system, especially through dynamic story-based content, is not possible, nor is instant order and payment management possible. Furthermore, current systems lack the ability for users to create their own orders while sharing a story. Businesses need a comprehensive social media-supported platform that will transform social media interactions into commercial benefits, reduce reliance on POS devices, and enable all ordering, menu, and promotion management from a single digital dashboard. Therefore, the state of the art lacks a structure that integrates story sharing with order creation. Self-ordering through stories is not possible, and there is no social media-supported platform that offers businesses order management, menu control, and payment processing from a single dashboard without a POS device. A review of patent documents related to some indirect and partial competitors in the state of the art reveals: Instagram: Content sharing and business profiles are available, but it lacks the direct ordering, loyalty system, or integrated business management features offered by our invention. TikTok: Offers entertainment-focused video sharing but doesn't offer direct ordering and delivery interaction with local businesses. Facebook (Meta Platforms Inc.): While it has event organization features, it falls short of modern business integration and story-based ordering systems that appeal to young user dynamics. Related patents include US766912382 (Display of advertising and informational messages on social networks) and US943694582 (Interactive map-based search and advertising system). These patents focus on news feeds, advertising, and map-based search systems on social networks and don't cover direct physical ordering and delivery processes through stories. On the other hand, applications like Yemeksepeti / GetirYemek only offer food ordering functionality. They lack social interaction, content creation, discovery, and community functions. Google Maps / Google Business provide basic information for businesses; however, it does not include social connection, content interaction, or community building features. Patent US943694582, granted by Google (Google LLC), relates to interactive map-based search and advertising systems. Zomato / Foursquare offer venue discovery and reviews but do not include user community, content-based interaction, or digital transformation modules. Meetup offers event creation and community building, but lacks business integration and social media-based ordering functions. Eventbrite provides ticketed event management, but its social discovery and local experience infrastructure is weak. Patent US958314281, granted by TikTok (TikTok lnc.), is for a social media platform for video creation and sharing and similarly does not offer an integrated social-commercial ordering system. Patent US773913982, obtained by Amazon (PlanetAll), describes a general social networking system. None of these platforms or documents describe a system that combines the core innovative elements of our invention—ordering for both others and yourself via stories, physical delivery, and a POS-free integrated management panel for businesses. Purpose of the Invention: This invention fundamentally relates to a technical field that combines social media platforms, mobile applications, e-commerce systems, payment infrastructures, POS (Point of Sale) device integration, and the digitalization processes of local businesses—developed to offer a new system design that eliminates the aforementioned problems and solves existing ones. The primary purpose of this invention is to combine social media interaction with physical delivery by offering ordering for both others and yourself via story sharing. Another purpose of the invention is to enable users to create instant orders for themselves, both as gifts/treats for others, and directly through a social media story. Another purpose of the invention is to enable businesses to easily manage orders, menus, stock status, promotional campaigns, and payments through a single, integrated digital management panel (Business Digital Panel), eliminating or reducing the need for POS devices. Another purpose of the invention is to enable users to create their own orders and have them physically delivered to the same location or partner businesses where they share their stories. Another purpose of the invention is to transform social media posts into commercial opportunities by supporting the local economy and tourism. Another goal of the invention is to increase user satisfaction (Customer Experience) by enriching the ordering experience via Story sharing with dynamic menus, secure payment (Instant Ordering and Gift Delivery), and push notifications. Another goal of the invention is to provide secure and verified order delivery through technologies such as QR code systems. Another goal of the invention is to support businesses' management and marketing strategies by providing data-driven analytics on user behavior (User Interaction) and ordering habits (Digital Marketing). Another aim of the invention is to create a social scoring system (Socio-Economic Interaction, Community Building) that incentivizes users by scoring social interactions (story shares, User Generated Content (UGC), orders, etc.) (Loyalty Program) and allows businesses to organize campaigns for loyal customers. Story-Based Interactions through a Digital Ordering System EXPLANATION OF THE FIGURES Figure 1: Shows the representative flow diagram of ordering a product from another user via a story. Figure 2: Shows the representative flow diagram of the process of a user placing an order for themselves and paying with a QR code. Figure 3: Shows the representative technical diagram of the process of generating and verifying a QR code containing an encrypted token. Figure 4: Shows a representative interaction diagram showing the integration of the business management panel with order and content management. Figure 5: Shows the data flow of the AI supported social scoring system. Figure 6: Shows the HiveUP APL architecture and data flow. Figure 7: Shows the general architecture of the story-based ordering and ordering process. Detailed Description of the Invention The invention relates to a technical field that brings together social media platforms, mobile applications, e-commerce systems, payment infrastructures, POS (Point of Sale) devices integration and the digitalization processes of local businesses. More specifically, the invention allows users to create product/service orders for themselves and others via social media posts (stories) and to physically receive these orders; It also encompasses an integrated social-commerce platform system where businesses can manage orders, menus, and promotional campaigns via a management panel. This invention is an innovative social-commerce platform system that integrates social media interactions, particularly story sharing, with physical product/service ordering and delivery processes. The system consists of a series of integrated modules designed for both end users and local businesses. This invention is an innovative social-commerce platform system that combines social media story sharing with order creation and physical delivery, allows users to place orders for both others and themselves, and provides businesses with an integrated management panel, enabling them to process orders and payments without the need for a POS device. The basic operation and elements of the system are as follows. Users can share social media stories through the mobile application of the platform. During this sharing, the Story Module comes into play. The Story Module allows users to create photo-, video-, or text-based stories, add various interactive elements to these stories, and automatically add location information within the story. Before or during story sharing, the Location Module detects the user's current location using GPS data or allows the user to manually select a location. This location information is used to verify the business with which the story was shared or to link the story to relevant partner businesses. By matching story shares with users' GPS location data, it verifies the authenticity of the shared location and links the story to partner businesses. This gives the story a geographical context. In the system, User A shares a story within the app while at a location or business and adds their current location information to their post. Location information is captured via GPS or selected by the user and processed as metadata in the story. The application determines the relevant BusinessID by matching the location information with the platform's business database. Thus, the shared story is associated with a specific business (location). At this stage, the system automatically assigns a specific business (location) to the story content. Figure 1 shows a representative flowchart of the process of ordering a product from a story shared by a user on the platform. In this flowchart, User A transmits a story and location information to the HiveUP server through the application. User B, who watches the story, accesses the menu in the story interface. User B selects a product from the listed menu, places an order, and completes the payment transaction through the application. The HiveUP server forwards the order to the relevant business and sends a notification to User A, informing them that a product has been ordered. The story allows users to place orders for both their friends (others) and themselves. Users can place orders (send gifts) for friends viewing the story, as well as place orders directly from that business while sharing or viewing the story. When the user clicks the order button, the Social Trigger Engine initiates the ordering process. It becomes active when the story is shared, triggering the ordering process. Once the ordering process begins, the Dynamic Menu Engine is activated. This engine instantly displays menu and inventory information defined and updated instantly via the Business Admin Panel (or integrated with the business's existing POS system). The user sees only the products currently in stock and available for ordering. The user selects the desired products from the menu. Using the Dynamic Menu Engine, it presents the current digital menu of the business to which the story is associated to User B. When User B clicks the "Order" button, the application makes an API call to retrieve the product and inventory data for the relevant BusinessID from the server. User B's selected product(s) and payment information (e.g., registered credit card) are also transmitted to the server via the REST API. Payment is securely processed by the platform's integrated Payment Processor. Once the order is successfully placed, the system sends a real-time notification (push notification, SMS, or email) to User A via the Notification Service. The notification includes information about who ordered which product and where it can be picked up. Once the order is successfully placed and payment is completed, the Notification System sends instant notifications to both the user who placed the order and the relevant business via the Business Admin Panel, informing them of the order's receipt, preparation, and delivery. On the business side, the Business Admin Panel plays a central role. This panel allows businesses to manage orders, menus, promotional campaigns, and discounts from a single dashboard. On the business side, the order is instantly visible through the Business Admin Panel. This allows the user sharing the story to be physically present, business staff can notify User A that their order is ready, or the product can be delivered to their table. This is a "sending a gift" scenario that transforms social media interaction into a real-time commercial action. For example, User A shares a story while having coffee at a cafe; User B sees this story, says, "This coffee is on me," and orders A a coffee through the app. The entire process takes place end-to-end within the app and is managed securely. This integration between story sharing and ordering provides a new interaction model not found in existing systems. The system also includes a self-ordering and QR code payment system. The HiveUP platform has an infrastructure that allows users to self-order and complete payment via QR code without needing a physical POS device. In the system, users view the digital menu by selecting the business they are currently at or want to visit within the app. The menu for the relevant business is dynamically presented based on the business's current stock and product information (managed from the Business Panel). When the user adds a product to their cart and confirms the order, the app generates a unique QR code. In this regard, Figure 2 illustrates the flowchart for a user placing an order via a mobile app and paying with a QR code at the store. The user creates an order by selecting product(s) in the HiveUP app and confirms their cart. The server generates an encrypted QR code token specific to this order and displays it to the user. When the user arrives at the store, the QR code in the app is displayed to the cashier. The device at the store scans the QR code and sends the order data and token to the HiveUP server. In the background, the server automatically processes the payment from the user's predefined payment method (or verifies it if a payment has already been received) using the integrated Payment Processor. When the payment is successfully approved, the server notifies the store panel that the order has been paid and that the product can be prepared. At the same time, the user application receives an order confirmation notification. At the end of this entire process, the user receives their product simply by scanning the QR code, without having to pay at the physical POS device or cash register. At this stage, QR Code and Encrypted Token generation occurs within the system. QR codes generated within the system provide a secure identity and payment verification mechanism thanks to their encrypted token structure. When an order is confirmed, a JSON data packet containing the relevant order and user data is generated on the server side. This data packet typically contains fields in the format {"user_id": "order_id": "business_id": "timestamp": ...}. For example, this packet stores UserID, OrderID, BusinessID, and a timestamp containing the token creation time. The generated JSON string is encrypted using a strong cryptographic algorithm. The preferred method is the AES symmetric encryption standard using a 256-bit key (e.g., AES-). The encryption key is kept secure only on the server side, and the authority to decrypt the token is granted only to the central system. The encrypted data is converted into readable characters (e.g., Base64 encoding) and turned into a token, and this token is encoded in a QR code. To illustrate this, a representative technical diagram for the creation and verification of a QR code containing an encrypted token is given in Figure 3. The data packet in JSON format (user, order, business, and time information) is first prepared on the server side. This packet is encrypted with the AES-256-CBC algorithm to obtain a secure token, which is then converted into a QR code. This QR code, unique for each user and order, is presented to the user in the application interface. When the user scans the code on a device within the business (e.g., the QR scanning module of the business panel), the encrypted token within the code is transmitted to the Verification Module on the server. The server decrypts the token using its private key and obtains information such as OrderID and UserID within it. It then uses this information to verify that the order is valid and paid, and that the token has not expired. From the moment the token is generated, it is limited to a 24-hour validity period for security reasons. The server verifies the token's expiration date by looking at the timestamp. If the verification is successful, an "approved" response is generated, and the delivery process for the relevant order is initiated. If the token is invalid or expired, the system rejects the order. This mechanism ensures that each QR code is single-use and cannot be copied or reused. The encrypted QR token structure enhances security. This is critical. Thanks to the encrypted content, the data within the QR code cannot be read by third parties; meaningful information can only be accessed when the HiveUP server decrypts it with the correct key. This prevents potential fraud attempts (e.g., manual modification of token data) because even the slightest change will compromise the token's integrity and server-side security. Furthermore, since the token is limited by its lifetime, even if it is compromised, it expires after a certain period. All these measures ensure the secure, fast, and error-free operation of the QR code payment and verification system. The implementation of this infrastructure plays a crucial role in achieving the HiveUP platform's goal of POS-free payments. Consequently, when the payment phase for selected products is reached, the Payment Infrastructure is activated. This infrastructure enables secure payment via credit/debit card or other digital payment methods integrated into the platform. The business's POS system Payments and order confirmations are made possible through the management panel without the need for a device. The business management panel is compatible with mobile devices. Through this panel, businesses can; see, accept, update and manage their orders (through the Order Management Module) in real time. They can track their order status (preparing, ready, delivered, etc.). They can create and update their menus (products, prices, descriptions, images). (In connection with the Dynamic Menu Engine (4)). They can track their stock status. They can create and manage promotional campaigns, discounts and loyalty programs. They can receive payments and confirm orders without the need for a POS device. Customer data and order history are analyzed in connection with the Analytics Engine. When the order is ready, the user can physically go to the business and collect their order by scanning the QR code (18) at the business premises and provide identification. Verification is performed and the order is delivered. The business generates a unique QR code for the order or presents the user with a QR code associated with the order. Throughout this process, the Analytics Engine analyzes user and business data and provides reports to the business. Businesses can track user behavior and ordering habits. It analyzes user behavior (story shares, order preferences, interactions, etc.) and business performance (order volume, popular products, campaign effectiveness, etc.) using anonymized or permissioned data. For this purpose, the HiveUP platform has introduced a mobile management panel for local businesses to easily manage incoming orders and their content. This panel is a separate application module or app with secure access for business users (e.g., cafe owners or authorized personnel). The Business Mobile Panel provides real-time order tracking and control of business data. It has functions. Through the panel, businesses can manage their digital menus, perform operations such as adding new products, updating prices and stock, temporarily closing products, or defining promotions. These changes are instantly processed in the central database, and the menu in the user application is dynamically updated. Figure 4 shows a representative interaction diagram showing the integration of the Business Management Panel with order and content management. Through the Business Mobile Panel, businesses can view and update menu and stock data. These requests are forwarded to the HiveUP server, which records the relevant changes in the central database in the background. Furthermore, when users place a new order, the server immediately forwards it to the business panel; a new order notification appears on the panel (real-time updates). After viewing the incoming order, the business panel user begins preparing it and, when ready, displays the order status as "ready" or "delivered" in the panel interface. This status update is sent back to the server and stored in the database as a record of the order status. If necessary, readiness information is sent to the user as a notification. The business management panel also features a QR code scanning feature. When a customer presents the QR code on their app to the business, they can scan it with the camera module within the panel app to confirm payment. The panel application operates in constant synchronization with the server, tracking every new order, payment status, and cancellation/return status. This allows the business to manage all digital ordering processes through a single application, eliminating the need for a separate POS device, cash register, or other software. The panel also provides access to a list of past orders, revenue and sales reports, and customer reviews (if applicable). In this respect, it functions as a comprehensive, business-focused control panel. All data is securely transferred to the server through calls. Because it's transferred, remote menu updates or reporting are also possible. For example, the operator can update stock status or review daily sales from the application while outside the store. Communication between this panel's mobile application and the server is provided via RESTful API in JSON data format. A detailed explanation is provided below. The panel can also use websocket or push notification mechanisms when necessary to receive real-time order notifications. For example, when a new order arrives, a notification is triggered on the server side to the business's active panel session. This allows the business to receive instant alerts without the need to constantly refresh the screen. The HiveUP business panel combines functions such as menu management, order management, inventory tracking, promotion control, and payment confirmation into a single mobile interface, providing local businesses with the advantage of digital transformation. The invention also includes a Social Scoring System and an artificial intelligence-based analysis engine. It has features that allow users to monitor story shares and user activity to ensure compliance with ethical values and analyze user behavior. It allows users to earn social points from their shares and order transactions. It supports businesses in prioritizing users with high social scores for promotions. This encourages users to use the platform actively and positively and provides an effective loyalty and targeting tool for businesses. The Social Trigger Engine is a trigger engine that integrates story shares into the dynamic menu and payment infrastructure. It initiates the ordering experience when a story is shared. The Social Scoring System is powered by artificial intelligence (AI). This system analyzes users' interactions and behaviors within the app and assigns a dynamic social score to each user. The scoring algorithm can be designed as a machine learning model that considers various inputs or a rule-based decision engine. The primary user activity data considered is These are: - the number of shared stories and their popularity (e.g., the number of views and likes of the stories), - orders placed through the application (sub-criteria such as frequency, number of different businesses, the number of gift sending), - interactions with businesses (e.g., check-in, leaving comments/ratings, inviting friends) and feedback provided by the user. Business interaction data can also contribute to the scoring system. For example, if a user frequently orders from a particular business, their interaction with that business is considered high. Figure 5 shows a representative diagram of the data flow in the AI-supported social scoring system. Data such as users' story sharing, order history, comments and ratings, and interactions with businesses (e.g., checking in at a venue, participating in a business's campaigns) are collected and analyzed using Artificial Intelligence. This is fed into the Scoring Engine. This engine processes incoming data via a machine learning model or rule-based algorithm and calculates a score for each user. The calculated score is recorded in the central Score Database and reflected in the user profile. The system dynamically updates the score as new activities occur. This way, the score always represents the user's current behavior. This social score can be used in multiple ways within the platform. For example, users with high scores can earn badges like "community leader" or "top supporter" or gain access to certain discounts and promotions. Businesses can define special campaigns for loyal customers with high scores. The scoring algorithm can also identify negative behaviors (e.g., frequent order cancellations or sharing inappropriate content) and reflect them in the score. In this respect, the system has become a mechanism that encourages ethical and positive interaction. The artificial intelligence model analyzes user behavior. It improves scoring accuracy over time by learning patterns. For example, machine learning determines which interactions contribute most to the platform's growth or which users have influencer potential, making the scoring formula adaptive. Technically, because this module will process large amounts of user data, a distributed data infrastructure and, if necessary, real-time stream analysis are used. For privacy reasons, scores are calculated using anonymized data, taking care to protect personal data. For example, suppose User X shared 10 stories in the last month, placed a total of orders from 5 different businesses, and recommended the app to 3 friends. The system can identify this high activity and assign the user a HiveScore of 85/100. On the other hand, a less active user is given a lower initial score, but their score increases as they continue using the platform. This social scoring system helps HiveUP build user loyalty. It is a key component that enhances and provides valuable insights to businesses. All components of the HiveUP platform are connected by a scalable, standards-based RESTful API architecture. Both the end-user mobile application and the business dashboard use this API to communicate with the server. API requests are based on data exchange in JSON format over HTTP, and each request must be authenticated by a specific user or business. In other words, all endpoints require secure access; users make requests with an authentication token (e.g., JWT - JSON Web Token) or session key, and businesses access the API by logging in with their own credentials. This way, the authorization and access rights of the user or business are checked for each API call (user and business information is mandatory). The API design, It consists of understandable and purposeful endpoints. For example, a business's menu can be retrieved with GET /api/businesses/{id}/menu. A new order can be created with POST /api/orders. The status of an order (ready, delivered, canceled, etc.) can be updated with POST /api/orders/{id}/status. All responses are returned with HTTP status codes and the necessary information in the JSON body. A central database on the server side (e.g., SQL or NoSQL-based) stores incoming and outgoing data, etc., in all these transactions. The API architecture is designed to be stateless. Since each request carries the necessary identity and context information, the server does not have to keep a user's session information on the server. This increases scalability. Figure 6 shows the representative API architecture and data flow of the HiveUP system. User Application and Business Application (Mobile Panel), HiveUP It sends HTTP GET/POST requests to RESTful API endpoints on its server and receives responses in JSON format. The server validates incoming requests and retrieves or updates the necessary data from the database. For example: - When a user wants to display a menu, the application can retrieve the menu for business with ID 45 from the server database and display it as JSON. - The business panel can query that business's orders with GET /api/orders?businesses=45. When critical events occur, the server can send POST requests to third-party URLs via a webhook system. For example: when a new order is created, if the business has defined a webhook URL to integrate its system, the HiveUP server POSTs to that address; {"event": "new_order", "order_id": 12345, "business_id": 45, ...} can send notifications. The webhook target is a defined integration point on the receiving end, which receives the event from the server and responds with "200 OK." This mechanism allows HiveUP to integrate with external systems (for example, a business's kitchen display, printing system, or CRM software can be notified via webhook when an order arrives). Webhooks can be verified with shared secret keys or signatures for security purposes, allowing the recipient to confirm that the incoming request truly originated from HiveUP. Another key component of the API architecture is the ability to integrate callbacks and push notifications with the webhook system. While webhooks are primarily used for external system integrations, push notifications to end users are delivered via Firebase Cloud Messaging or Apple/Google push services (e.g., a notification to a phone for an order status update). All these architectural components work together to ensure a seamless data flow between HiveUP's various modules. The system is built for horizontal scalability (multiple server instances, load balancing, etc.) and optimized for stable operation even under high traffic. As a result, the backend of the HiveUP platform was designed with modern REST API principles and an event-driven approach, creating a secure and flexible infrastructure. All processes within the HiveUP platform have an integrated architecture that begins with user story-based triggers. In this architecture, the first step required to initiate an order flow is for a user to share a story. In other words, the order cycle on the platform is triggered by a social interaction (viewing a story), not by a product search as in traditional applications. User identity and story data are the connecting elements at the very beginning of the process; each story is tagged with a specific user ID and location (business) information, ensuring that future orders are correctly routed. In short, the process involves a multi-step interaction between the user sharing the story, the user viewing the story, the relevant business, and system modules. Figure 7 shows the general architecture of the story-based ordering and ordering process on the HiveUP platform. Step by step in this architecture: The first step is for User A to create a story. While creating the story content, the application captures the user's ID and GPS location and identifies this story with a BusinessID. The story is now content associated with a specific business and belongs to that user's account. During the story triggering phase, the "Order" or "Order" button becomes active for User B, who is watching the story. When User B clicks this button, the application retrieves the menu data from the BusinessID linked to the story and opens an ordering interface. At this point, User B cannot select a different location or business other than the business identifier in the story—the system architecture is designed to prevent adding additional locations. This way, the order is directed precisely to the location tagged in the story. User B selects the product(s) from the drop-down menu and proceeds to the order and payment step. Payment is processed using the in-app payment infrastructure, as detailed in Chapters 2 and 3, and a QR code containing an encrypted token is generated when the order is approved. During the business approval phase, the order is instantly displayed on the relevant business panel. The business sees the order on the panel and begins processing it. When User B arrives, the business displays the QR code in the app. The business scans the code with the scanner on the business panel, verifying that the order was indeed placed by 0 users and that payment is complete. This step is fast and secure because it uses the system's own security tokens, eliminating the need for a physical POS device. The final step is order completion. If User A is the gift recipient, they receive the order; If User B receives their order, the process is complete. At this point, HiveUP can reflect these interactions in the social scores of the relevant users (for example, the score of the user who sends or receives a gift increases). Furthermore, the order data is processed in the analytics engine, creating a sales record for the business. Critical to this architecture is preserving the context that begins with story sharing and ensuring end-to-end tracking of the entire process. The location determined in the story phase is stored as a locked parameter by the system and is not changed throughout the order flow. This ensures that the order placed by User B belongs only to the business specified in the story. This is a key rule that ensures the platform's reliability and consistency—users cannot accidentally send orders to locations other than the location they saw and interacted with in the story. Additionally, because user IDs (UserIDs) and content/order IDs are transmitted to the system at all steps, any errors or discrepancies that may occur at any point can be tracked (for example, if the payment cannot be verified, the order is canceled and the relevant users are notified). In conclusion and summary, the basic relationships between the elements of the invention are as follows: The Story Module and the Location Module work together to add a location to the story post and enable geotagged story sharing. The Beverage Order/Self-Order Button, integrated with the Story Module, initiates the user's ordering experience through the story. The Dynamic Menu Engine integrates with the Business Management Panel or POS system, enabling inventory control and menu display. The Payment Infrastructure works in conjunction with the Business Management Panel to complete payment transactions without the need for a POS device. The Order Management Module monitors the current status of orders via the administration panel and works in coordination with the Notification System. The QR Code Delivery Module securely handles the physical delivery of orders. The Analytics Engine collects and analyzes all data through the Business Management Panel and system modules. The Social Trigger Engine initiates the ordering process with story sharing and integrates all modules. The Social Scoring System integrates with the Story Module, the Social Trigger Engine, and order data to analyze user behavior and shares. Supported by the Analytics Engine, the score data is reported to businesses. All these modules store and manage user, business, order, menu, and interaction data in a database. A representative application summary (HiveUp system) illustrating the invention's operating principle is provided below. The HiveUp system is an innovative social-commerce platform that integrates social media sharing (stories) and physical ordering experiences, initiating and managing both individual and social ordering processes through story sharing. A user (for example, Ayse) shares a story while sitting at a cafe through the HiveUp mobile app. The Story Module and Location Module link the story to that cafe (verified with GPS data). Using the Beverage Order/Self-Order button within the story, Ayse can order both a cake for her friend Mehmet and a coffee for herself. When Ayse clicks the button, the Dynamic Menu Engine displays the cafe's current menu. Ayse selects the coffee for herself and the cake for Mehmet, and pays through the Payment Infrastructure (5). The Information System notifies Ayse that the order has been received and that Mehmet has received a gift. The cafe receives, approves, and prepares the order through the Order Management Module via the Business Management Panel. When the order is ready, the QR Code Delivery Module is activated. Ayse and Mehmet go to the cafe, scan their QR codes, and pick up their order. Throughout the entire process, the Analytics Engine analyzes the data, and the Social Scoring System updates Ayse's score. The Business Management Panel manages this entire process without the need for a POS device. Users don't need to share a story to place an order; they can access the menu of the business they choose through the app and create their own order. The social-commerce platform system in question can be easily adopted and used by local businesses, especially in the food and beverage (cafes, restaurants, bars), retail, entertainment, and tourism sectors. With this system, businesses can accelerate their digitalization processes (Digital Transformation), transform their social media presence into direct commercial revenue (Social Commerce), reach new customers, and build stronger connections with existing ones. They can increase their operational efficiency by eliminating the cost and complexity of POS devices. The order creation experience through story sharing is integrated with social media, allowing users to place orders themselves. It offers businesses the opportunity to digitize and acquire new customers. A dedicated management panel allows businesses to manage orders, menus, and promotions from a single screen. The management panel eliminates the need for POS devices, increasing operational efficiency. The management panel is compatible with mobile devices, allowing businesses to track orders from anywhere. Secure delivery is ensured through a QR code system. The analytics module provides businesses with data-driven management support. For users, the invention makes social media experiences more interactive and functional. It offers the ability to instantly place orders for themselves or their friends from places they like or have experienced. This creates an attractive use case, especially for young people and those who actively use social media. In the tourism sector, it allows tourists to discover local businesses in their area (Location-Based Services), share their experiences as stories (Experience Sharing), and easily place orders or receive services through these posts, contributing to the local economy. The invention can be developed, operated, and marketed by companies specializing in mobile application development, software, e-commerce infrastructure, payment system integration, and digital marketing. The system's modular structure allows for customization and scalability to meet different business needs. The HiveUp system combines social media experience, the digitalization of local businesses, and physical delivery, increasing both user interaction and revenues in cafes, restaurants, and similar businesses. In the tourism sector, it allows tourists to discover local businesses in their area and share their experiences through social media through story sharing. Story-based product ordering: In a social-commerce mobile application, this method allows one user to order a product from another user via story sharing. The method involves the following steps: the first user creates a story, adds location information, and sends it to the server, which then matches the story with a specific business ID (BusinessID); at least one second user views the story and interacts with the ordering button in the story interface; The application presents the current digital menu of the relevant business to the second user using BusinessID data related to the story; the second user selects at least one product from the menu, places an order on behalf of the first user and enters payment information; (The platform server transmits the order paid by the second user to the relevant business and notifies the first user with a notification; and the process is completed by the business preparing the order and delivering it to the first user. This method is characterized by establishing a real-time connection between the story sharing and the order process and restricting the order to be valid only for the location specified in the story. QR code-based self-service order and payment method: It is a mobile application-based method that enables the completion of the order given by a user on his behalf without the need for a physical POS device; it includes the following steps: the user creates an order by selecting a business through the application interface and selecting the product(s) from the digital menu; when the order is approved, the server creates a QR code containing a unique encrypted token related to the order in real time. (e) the server verifies the token data and digitally processes and approves the payment for the order in the background; the payment confirmation information is transmitted to the business panel, thus allowing the product to be delivered to the user. The method defined in this request provides a technical solution that enables the user to securely receive their own order, and the business to confirm the payment without using any POS device, thanks to the authentication and payment confirmation features with encrypted QR codes. QR code generation and verification method with encrypted tokens: The generation and verification of QR code tokens that securely represent an order data. It is a method for using the following technical features: when an order transaction is triggered, creating a JSON data packet on the server side containing the relevant user ID (UserlD), business ID (BusinesslD), order ID (OrderlD) and timestamp information; (b) encrypting this data packet using a strong symmetric encryption algorithm, preferably AES-256-CBC algorithm and using a 256-bit private key to obtain an encrypted token; encoding the obtained encrypted token into a QR code and displaying it on the user device; when the QR code in question is scanned by an authorized device, transmitting the encrypted token data in it to the server as is; the server obtaining the original JSON data by decrypting the token with its own secret key and verifying the OrderlD, UserlD, BusinesslD and timestamp information in it; It checks the validity of a token within a predefined period (e.g. 24 hours) from the moment it is created and considers expired tokens invalid; if the verification is successful, the relevant order is confirmed and the system marks this token as used. This method is designed to ensure data confidentiality and integrity by encrypting the QR code contents with an industry-standard algorithm such as AES-256-CBC and ensuring that only the authorized server can read it. It prevents fraud thanks to token-based verification and provides a secure payment/identification mechanism. Artificial intelligence-supported social scoring method: It is a computer-based method that evaluates user interactions on the HiveUP platform and provides scores; it includes the following steps: various activities of the user on the platform (story sharing, orders placed through the application, orders sent to other users, business (e.g., comments, friend invitations) as interaction data; interactions with businesses (repeated orders from a specific business, check-in records, feedback, etc.) are added to the relevant user profile; this multi-dimensional data set is analyzed periodically or in real time by an artificial intelligence scoring engine - the engine uses a machine learning model (e.g., decision trees, artificial neural networks) or an expert rule system to make inferences about which user behaviors are more valuable for the platform; as a result of the analysis, each user is assigned a social score according to their current behavior, the score is calculated as a numerical value (e.g., in the range of 0-100) or as a level; the calculated score is stored in the user profile database and displayed to the user (and businesses, where allowed) in the application interface; the score is dynamically updated as the user has new interactions, thus observing behavioral changes over time. Ensuring that the results are reflected in the score; triggering additional processes such as assigning badges, levels or awards to users based on the score height (optionally). This system is a technical method that automatically evaluates user behavior at the intersection of social media and e-commerce and converts it into a scoring metric. It distinguishes itself by creating an incentive feedback mechanism for each user using machine learning and big data analysis. REST API-based platform and webhook integration system: HiveUP is a system related to the server infrastructure of the social-commerce platform and includes the following technical elements: the REST API layer, which enables communication between client applications (user mobile application and dashboard) and the server. This layer contains numerous endpoints that transmit data in JSON format over the HTTP protocol, and user or business authentication is required for every request. a central database where user data, business data, product menus, order and payment information is kept, and server-side API operations perform CRUD (create, read, update, delete) operations on this database; an authentication module that ensures each request is authorized using access tokens, JSON Web Token (JWT) or similar technologies issued through OAuth 2.0 or a similar method for API security; a webhook mechanism used to notify external systems when defined events occur on the platform server, such as an automatic trigger that sends a POST request over HTTPS to a pre-registered URL when a new order is created or the order status changes; additional security steps such as adding a signature to each request or checking a shared secret key to ensure the confidentiality and integrity of webhook requests; A push notification or socket connection infrastructure (other than webhooks) that may be required to notify client applications of data generated by an API transaction (e.g., sending a push notification to the user application for an order status change); and a monitoring/logging module for logging and monitoring all API calls and webhook transactions. This system ensures the platform's modularity and scalability by providing a standard HTTP-based data flow between different devices and components. It also provides a technical solution that allows third-party applications to react in real time to events within HiveUP through webhook integration. Integrated social-commerce platform system with story triggers: This system is a system related to the integrated structure of the HiveUP platform and involves the interactive operation of various modules that integrate story sharing and physical product ordering processes in real time. The system comprises at least the following components: Story Module, a client-side software component that allows a user to create a photo/video story via a mobile device and tag a business location along with GPS data; Location Matching Module, an infrastructure that compares location information obtained during a story with the platform’s business database to assign an appropriate BusinessID and associates the story with a geographic location; Social Trigger Engine, an event-driven software module that manages interaction elements such as an “order” button integrated into the story and initiates other related user actions (order for someone else or order for yourself) when a story is viewed; Order and Menu Management Module, a server-side component that handles the order creation process triggered by user interaction, presenting the relevant business’s digital menu and creating an order record for the selected products; Payment and QR Code Module, the component that receives payment for the created order via in-app, generates QR codes by encrypting order data and manages payment confirmation in integration with QR scanning; Business Management Panel Module, a business-specific client interface that can instantly view and manage incoming orders, make menu/promotion/stock updates and confirm order delivery via QR code scanning (its features are defined in Request 4); Notification and Message Module, the infrastructure that communicates order statuses and user interactions to relevant parties in real time (via mobile push notification, SMS or e-mail); The Social Scoring and Analytics Engine, an artificial intelligence-powered component that analyzes user behavior by collecting all interaction data on the platform and generates scores, the API and Integration Layer, and the server-side infrastructure that enables all these modules to communicate with each other and with external systems via RESTful services and webhooks. The system described in this claim is characterized as an innovative social-commerce platform that, thanks to the integrated and synchronized operation of the mentioned components, enables a process that begins with social media story sharing to transform into digital ordering and QR code-based payment through location-based matching and ultimately to physical product/service delivery. The system offers a technical solution and a new interaction model for both users and businesses by uniquely combining story content and e-commerce transactions. HMUP Suuiiwiu sam unu `~ Odam au .ip-n. (Stem fame» inim "Çankiri/honeymoon (Uma ünal!. Stacy nn Sis-:li &forget (You opened the rate!. "Int approval assigned OR school-II" Business Mobile Panel s order status update New order notification (ready, delivered) (instant update) HiveUP Server User Activity Data Business Interaction Data (Story, Order, Comment, etc.) (Check-in, feedback) Ni entry /Gi entry (Machine Learning Model) Score calculation dynamic update) User Application Business Application (Mobile) (Mobile Panel) HTTP API Invoked API Calls (GET/POST, JSON data) (Business transactions) HiveUP Server (REST API) Webbook notifications ' (e.g.: new order event) "Response 200 OK Data read/write (user, order, etc.)Webhook Target (Integration) base TR

Claims (1)

1.