Technical Implementation and Patent Claims for Commerce Services
Patent review for commerce services focuses on concrete systems that process order, payment, settlement, inventory, delivery and recommendation data, rather than sales methods alone. The specification and claims should explain how transaction rules are executed by servers, user devices, databases and external systems.
Describe business methods as technical processing
A discount policy, brokerage arrangement or revenue-sharing rule alone may remain a business rule. Identify input data, processing actors, sequence, intermediate data and outputs. Korea's official business-method invention guidance (in Korean) likewise describes business-method inventions as business ideas implemented through information and communications technology, such as computers and the internet.
For example, do not describe automatic coupon issuance merely as rewarding customers according to their tier. Explain how the system receives order history and inventory data, identifies eligible product groups, checks overlapping discounts and budget limits, generates coupon data with an expiry date, and applies it through a payment server.
Identify protection targets by technical area
| Area | Technical configuration to describe | Results to verify |
|---|---|---|
| Recommendations | Collect behaviour, purchase and return data; generate features; filter and rank candidate products. | Response time, recommendation accuracy and reduced stockout or return risk. |
| Orders and payments | Order-state transitions, payment approval and cancellation, partial refunds, duplicate-request prevention and failure recovery. | Prevention of double charging, processing consistency and recoverability. |
| Settlement | Calculate amounts for sellers, platforms and partners; account for fees and taxes; generate corrections and audit logs. | Fewer errors, traceable calculations and high-volume processing performance. |
| Inventory and logistics | Reserve stock across warehouses, select dispatch locations, consolidate shipments, restock returns and integrate external systems. | Stockout prevention, shorter delivery distances or times and inventory synchronization. |
| Reviews and trust | Verify purchases, detect abnormal patterns, analyze text and images, and update seller metrics. | Identification of false information and reproducible decision grounds. |
Clarify actors and data flows in the claims
Commerce systems involve buyer and seller devices, platform servers, payment service providers, logistics providers and settlement systems. If the actor for each step is unclear, it becomes difficult to determine whether one actor performs the entire method or to map the claim to the actual service.
Place the distinguishing inputs, decision conditions, processing and outputs in the independent claim. Dependent claims can elaborate data structures, exception handling, real-time updates, security checks, model training and external integration. Consider server or system claims and computer-readable recording-medium claims alongside method claims, while avoiding mere repetition of the same function in different words.
Exception handling is part of the invention
Distinctive features often emerge in payment retries, inventory contention, partial cancellations, seller withdrawal, settlement corrections and network delays. Describe state changes, retry conditions, duplicate-prevention identifiers, rollback or compensating operations, and log retention.
For AI features, go beyond the model name. Specify training and inference data, preprocessing, features, outputs, threshold application and resulting system actions. Distinguish processing structures that survive a model replacement from configurations tied to a particular model to support claim-scope design.
Prepare implementation-level materials before filing
- Sequence diagrams from user request to processing result
- Architecture diagrams connecting services, databases and external APIs
- Definitions of input fields, intermediate states and output data
- Problems in existing approaches and the processing steps that resolve them
- Verifiable effects such as error rate, processing time and resource use
- Disclosure, launch, proposal and demonstration schedules and related materials
Screen flows alone cannot adequately explain differences inside a server. Review development documents, API specifications, state-transition tables and test results together to keep claims aligned with the product. Before public disclosure, identify the materials and disclosure dates that may affect novelty.
