GlobalEdge is the system of record for all customer records. Customers must be created/edited in GE; those records then sync to EvoX.

A new customer request form on the storefront routes to a designated contact at the client, who creates the account in GE — the end user then receives a welcome email with login instructions. EvoX does not support guest checkout.

The GE Charge Customer value becomes the Account Number in EvoX; the GE Site Customer value becomes the Seller Reference.

Each GE customer syncs as two EvoX records: an Account (from the customer's core attributes — AR terms, PO required, etc.) and an Address record. Address type is set automatically:

GE Customer Locations can optionally sync to EvoX as additional shipping addresses. Shipping addresses created in EvoX can optionally sync back to GE as Customer Locations — once synced, they're only editable from the GE side.

A field on the GE customer record can be used to exclude a specific record from syncing, if needed.

GlobalEdge is the system of record for contacts. Contacts are created/edited in GE and synced to EvoX.

The email on the Customer Portal tab becomes the login ID for both the EvoX storefront and the GE Customer Portal (single sign-on).

When creating a contact in GE with EvoX enabled, set status to Active, enter a unique login ID, and assign a Customer Portal role to sync the contact. Leave status Inactive to skip syncing.

Store permissions are controlled by the EvoX store Role, which is separate from the GE Customer Portal role and can be adjusted per user inside EvoX.

GlobalEdge is the system of record for all sellable items. Items are created/edited in GE and synced to EvoX; catalog items ("item-other" records) can optionally sync as well.

An Ecommerce tab on the GE item/catalog record holds additional fields that can be mapped to EvoX (in addition to the standard summary tab fields already synced).

EvoX's Storefront Overlay feature can override sku, name, or description for the storefront only, without changing the underlying GE record.

Inventory quantities shown in EvoX come from a real-time lookup against the GE warehouses flagged for the integration. Clients choose whether Qty on Hand or Qty Available is shared.

Pricing shown in EvoX is a real-time lookup to GE, returning the same price GE would calculate if the order were entered directly there.

At checkout, EvoX sends the cart to GE for tax calculation — the integration works whether or not the client uses Avalara.

All EvoX orders are sent to GE.

COD accounts: must pay by credit card. EvoX is integrated with Fortis and can display previously stored cards from GE, or accept a new card (which replaces any previously stored card on the GE contact). EvoX sends a preauth only — GE staff capture the deposit at invoicing.

On-account checkout: the end user can choose to pay by card or place the order on account.

Accounts on HOLD or SOFT HOLD in GE can still place orders — the order comes through on Hold status so the client can resolve the credit issue with the customer rather than blocking the order outright.

Order History in EvoX pulls all GE order history for the logged-in account, with a detail view showing shipping information.

GE updates the EvoX order status on four events: order created, partially invoiced, fully invoiced, and order deleted (→ Cancelled in EvoX).

GE uses trigger tables (or CDC tables, depending on configuration) to track new/changed records. Edits only trigger a sync if a mapped field was changed — this depends on the Triggers tab being configured correctly for each edit method (Edit Customer, Edit Address, Edit Item, Edit Contact, etc.).

The EvolutionX crawler polls these trigger tables (recommended interval: every 1 minute during business hours) and processes records via the integration API. All requests are logged to the IntegrationLog table regardless of outcome.

Records that fail to process remain in the trigger table for 24 hours and are also written to the EvoxOutboundSyncState table. During that window the crawler keeps retrying, and the failure is visible on the EvolutionX Log screen — mark a record "reviewed" once the underlying issue is fixed to stop retries. If unresolved after 24 hours, the record is removed from the trigger table.

EvoX must be turned on in the GE licensing screen, which activates the required integration records and the EvoX crawler.

Configure the GlobalEdge app, Fortis payment app, Live Inventory endpoint, and Live Pricing endpoint in EvoX, plus JWT token sharing for GE Customer Portal single sign-on.

Because EvoX is the system of record for login credentials, disable the GE "New CP Login" notification — welcome emails for new contacts are sent by EvoX instead.

Branches and Locations must be configured manually in EvoX: a Location maps to a GE warehouse (using the GE warehouse code as the seller reference), and a Branch represents a physical pickup location — every Branch needs at least one Location.

Configure a single catalog (1000 – Own Catalog) and single supplier (1000 – Own Supplier) in EvoX; this phase of the integration doesn't support multiple catalogs/suppliers or third-party items.

GE Mfg codes map to EvoX Brands and must be created in EvoX, with the resulting EvoX Brand ID entered back into the GE Mfg record's Ecom ID field.

EvoX performs a preauth on all orders for customers without credit terms. If the merchant charges surcharges, a surcharge disclosure must be shown at checkout (card brand requirement).

Configure the Fortis payment method in EvoX for Preauth & Capture on Dispatch, along with the storefront label shown when a customer enters a new card.