Bidirectional Data Parity via Canonicalization for Ecommerce

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In multi-service connected environments, existing shipping management systems often lack robust functionality and fail to maintain data parity across multiple electronic marketplace systems, leading to issues like phantom orders and data inconsistencies due to incomplete or misinterpreted order records.

Innovation Solution

Implementing bidirectional data parity logic in conjunction with a canonicalization and order connection data structure, utilizing a canonicalization database and an order connection database to ensure accurate representation of order states and data across all systems, thereby recognizing all records for a particular order instance and maintaining data parity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If order aggregation is implemented across multiple electronic marketplace systems, then shipping management functionality is improved, but data consistency and parity deteriorate

Engineering Contradiction:

Improveshipping management functionalityVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary system that acts as a mediator between multiple electronic marketplace systems. This intermediary receives order data from various marketplaces, standardizes it using canonicalization, and distributes it to appropriate systems while maintaining data parity. The intermediary resolves conflicts and ensures all systems have consistent view of order states without requiring direct peer-to-peer synchronization between marketplaces.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transforms order data by changing its parameters through canonicalization - converting diverse order representations from different marketplaces into a standardized format. This parameter transformation includes normalizing field names, data types, and structures while preserving the essential order information, enabling consistent processing across systems without losing data fidelity.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If multiple records of the same order are maintained across systems, then system autonomy is preserved, but data parity and accuracy deteriorate

Engineering Contradiction:

Improvesystem autonomyVSAvoiddata accuracy

Core Design Contradiction:

Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent implements feedback mechanisms where systems continuously report their local order records to the intermediary, which then compares these records against the canonical order data. When discrepancies are detected, the intermediary provides feedback to the local systems to correct their records, ensuring data accuracy is maintained while allowing each system to retain autonomous operation of its local database.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent creates standardized copies of order data through canonicalization. Each system maintains its own records but also receives standardized copies from the intermediary that conform to a common data model. These copies serve as reference versions that ensure data accuracy across systems while allowing each system to maintain its own autonomous record-keeping.

Inventive Principle:

Principle #26Copying

3Productivity

If order aggregation is implemented, then shipping management capabilities are enhanced, but phantom orders and data errors increase

Engineering Contradiction:

Improveshipping management capabilitiesVSAvoidphantom orders

Core Design Contradiction:

ProductivityVSObject-generated harmful factors

Solution Approach 1:

The patent performs preliminary canonicalization and validation of order data before it is distributed across the system network. By standardizing and verifying order records in advance at the intermediary level, the system prevents phantom orders from being created in the first place, rather than having to detect and correct them after they appear in various systems.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The intermediary acts as a gatekeeper that filters and validates order data before allowing it to propagate to other systems. This intermediary layer prevents erroneous or phantom order data from entering the distributed system by implementing validation rules and canonicalization checks, thereby eliminating the source of data errors while still enabling order aggregation benefits.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11842381B1Systems and methods for bidirectional ecommerce parity

Publication Date: 2023.12.12 AUCTANE LLC

AI summary

Systems and methods which provide for bidirectional data parity in a multi-service connected environment using a canonicalization and order connection data structure are described. Bidirectional data parity logic using a canonicalization and order connection data structure with respect to a plurality of systems of a multi-service connected environment may provide for the state of a particular order and/or other data for that order being accurately reflected in each such system for which corresponding record is maintained. Using a canonicalization database and an order connection database, bidirectional data parity logic may recognize all records for a particular instance of an order as being for that order, and thus provide data parity for that order throughout all systems having a record for that order instance.