Back to Genius hub
Prepared for CTO review - ecommerce source identifiers and system movement

HandiProducts ecommerce data

Websites, WooCommerce, Amazon marketplaces, imports, order identifiers, and data movement

This document summarizes the existing documentation and the working data model for ecommerce orders across storefronts, marketplace channels, Genius ERP, Veeqo, FreightPop, Zoho CRM, GA4, and Google Ads.

Genius SO is the operational master key Woo prefixes normalize to WEB-##### Amazon IDs remain native Marketplace POs pass through raw

Executive Summary

6
WooCommerce storefronts

HandiRamp, HandiTreads, PetStep, GetBiggies, CargoVanRamps, and StopTheSlip have documented Woo/GA4 access and order rollups.

1
Production spine

Genius SalesOrderHeaderEntity.Code is the master operational key for jobs, invoices, shipping, BOLs, and fulfillment status.

5+
Identifier types in PO Number

Genius PoNumber holds source order IDs, vendor POs, marketplace IDs, internal references, and some legacy notes.

Modeling rule:

Do not model Genius PoNumber as a clean customer purchase-order field. Treat it as source_reference_raw, then derive normalized fields such as source_channel, source_order_id, customer_po_number, legacy_internal_reference, and source_reference_quality.

Existing Published Documentation

Source Systems

Websites / WooCommerce

HandiRamp, HandiTreads, PetStep, GetBiggies, CargoVanRamps, and StopTheSlip. Woo is the source for web order, billing email, order status, product, coupon, and ecommerce revenue context.

Marketplaces and imports

Amazon Seller Central, Amazon Vendor Central, Menards CSV, Home Depot, Lowe's, Wayfair/CSN, Grainger, Walmart, Chewy, Office Depot, and Do It Best. Most marketplace POs pass through into Genius unchanged.

Operational systems

Genius ERP, Veeqo, FreightPop, Zoho CRM, GA4, Google Ads, and related reporting feeds. Genius is the operational source of truth after order entry/import.

Data Movement Between Systems

Source order

WooCommerce, Amazon, marketplace, phone, or CSV

Orders originate in a storefront, marketplace, direct channel, or import file.

Import

Daily import, EDI, XML, CSV, or API

Source IDs are transformed or passed through depending on channel rules.

ERP spine

Genius Sales Order

SalesOrderHeaderEntity.Code becomes the master operational key.

Fulfillment

Veeqo, FreightPop, carriers, production

Fulfillment, tracking, package, BOL, invoice, and production data attach to the Genius SO.

CRM and reporting

Zoho, GA4, Google Ads, dashboards

CRM records, customer notes, attribution, and revenue reporting cross-check source and operational records.

Movement Primary key or reference Notes
WooCommerce -> Genius Woo order prefix stripped, then WEB-##### stored in Genius PoNumber Current documentation describes this as manual daily import/XML bridge work.
Amazon Seller Central -> Genius Native Amazon order ID, e.g. 112-0088405-9659408 ASC daily EDI flow imports into Genius, then shipping confirmation is uploaded back to Amazon.
Amazon Vendor Central -> Genius Short native alphanumeric PO, e.g. 75V9HXUW Different identifier shape from Seller Central; do not parse as a Woo or internal order.
Veeqo -> Genius Veeqo number -> WEB-{number} -> Genius PoNumber Daily Veeqo/Genius sync builds lookup files keyed both by Veeqo number and Genius SO code.
Genius -> FreightPop / carriers Genius SO, shipping header, shipment references Provides carrier, tracking, BOL, shipment status, and fulfillment context.
Genius -> Zoho CRM Zoho Genius_Order_Number equals Genius SO code Used by Universal Order Lookup and tracking-email Contact note writeback.

Source Identifiers And Transformations

Channel Source format Genius representation Transformation
HandiRamp.com HR264065 WEB-264065 Strip HR, prepend WEB-.
PetStep.com PS20935 WEB-20935 Strip PS, prepend WEB-.
HandiTreads.com HT40348 WEB-40348 Strip HT, prepend WEB-.
GetBiggies.com BG11718 WEB-11718 Strip BG, prepend WEB-.
CargoVanRamps.com CVR2303 WEB-2303 Strip CVR, prepend WEB-.
StopTheSlip.com STS##### WEB-##### Strip STS, prepend WEB-.
Amazon Seller Central 112-0088405-9659408 Native Amazon ID No Woo-style transformation. Updated by automated web/API import path.
Amazon Vendor Central 75V9HXUW Native short alphanumeric PO No Woo-style transformation.
Retail marketplace vendors Vendor PO, e.g. Home Depot, Lowe's, Menards, Wayfair, Grainger Vendor PO stored as-is Interpret with customer/channel context first. String shape alone is unsafe.
Inside sales / internal HR-81650 or numeric internal reference 81650 or 81650 - Customer PO Legacy/internal values may be stripped, concatenated, or mixed with customer PO text.

Analytics And Attribution Context

WooCommerce is the ecommerce order source of truth

Woo order counts and revenue are the primary source for storefront order totals. GA4 is used as a directional cross-check and attribution layer.

GA4 undercounts Woo on multiple sites

Recent health checks show GA4 purchase tracking exists, but GA4 order count and revenue can undercount WooCommerce totals. Use GA4 for channel quality, not as the only revenue ledger.

Google Ads ties to campaign attribution

Google Ads spend and campaign IDs are useful when Woo order attribution includes UTM, gclid, or campaign metadata. Some storefronts have no paid account or no paid orders in the sampled window.

Known Gaps And Cleanup Notes

Area Status Recommended handling
Genius PoNumber overload Known structural issue Normalize into derived source-reference fields instead of treating it as one clean business concept.
WooCommerce import automation Documented as manual daily import / XML bridge Automate once the current import rules and exception paths are locked down.
StopTheSlip billing code Uses WOO-STS for both Ship To and Bill To Verify whether it should align with other Woo stores that use shared WOO-AR Bill To.
YR rental monthly billing Historic reuse of one Genius SO breaks durable period-level lookup Forward fix is one new Genius SO per rental billing period, restoring a 1:1 Zoho SO to Genius SO join.
Duplicate/stale analytics properties Known cleanup candidates Keep active GA4 properties tied to live GTM destinations; delete confirmed orphaned properties only after admin review.