O2O Connections

O2O (Organization-to-Organization) links your Gloyd account directly with another company that also uses Gloyd. Once connected, business documents — RFQs, quotes, and orders — are automatically mirrored to the other side the moment they are sent, so neither company has to re-type what the other already entered. O2O is free and unlimited on every plan: there are no connection limits and no document delivery limits.

What O2O Is (and Is Not)

O2O is document mirroring, not status synchronization. Understanding the difference matters:

• When a document is sent, a copy is created once in the partner's account, with field mappings applied. From that point on, each company owns its copy independently.
• When your partner later acts on their copy (accepts a quote, confirms an order), your document does not change automatically. Instead, you receive a notification with an approval banner, and you decide whether to apply the change.

This keeps both companies in control of their own records while eliminating duplicate data entry.

Establishing a Connection

There are four ways to connect two Gloyd companies. All of them start from the Integrations → O2O page on the platform, or from the partner's portal.

1. Connection token

1. Open Integrations → O2O and generate a connection token. Tokens are valid for 24 hours.
2. Share the token with your partner over email or chat.
3. Your partner enters the token on their side. The connection becomes active immediately.

2. Email invitation

1. From Integrations → O2O, send an invitation to your partner's email address. Invitations are valid for 7 days.
2. Your partner clicks the link in the email and accepts (or declines) the invitation.
3. On acceptance, the connection is created for both companies.

3. API key

A portal admin can create an O2O API key from the portal. The partner company verifies the key on their platform and activates the connection. Product and unit mappings are auto-detected right after activation.

4. Portal connection request

If a customer or supplier already uses your portal and also has their own Gloyd subscription, they can request a connection directly from the portal:

1. The portal user verifies that their email belongs to a Gloyd account.
2. They submit a connection request.
3. You see the request on the Integrations → O2O page and approve or reject it. On approval, the connection is created and a contact for the partner company is added automatically.

Connection states

A connection is pending, active, paused, or revoked. You can pause a connection at any time (delivery stops, nothing is lost), resume it later, or revoke it permanently. Per connection, you can also toggle which document types are delivered (RFQs, quotes, orders) and turn automatic delivery on or off.

What Gets Mirrored, and When

Document	Delivered when	Arrives on the partner side as
RFQ	You send the RFQ	An incoming (sales) RFQ
Quote	You send the quote	An incoming (purchase) quote
Order	A quote is converted to an order	A sales order

The document type always flips direction: your purchase document is your partner's sales document. Delivered copies are marked with the o2o channel so you can always tell where a document came from, and a contact for the partner company is created automatically if it does not exist yet. Every delivery is recorded in an audit log.

See RFQ Management, Quotes, and Orders for what happens with each document after it arrives.

Field Mappings

Two companies rarely use identical product codes or terms. Field mappings translate values during delivery:

• Products — your SKU maps to your partner's SKU (auto-detected by SKU, MPN, or name match)
• Units — e.g. "pcs" on one side, "PCS" on the other (auto-detected by code)
• Contacts, payment terms, delivery terms — mapped between the two companies

Mappings are applied automatically during delivery; product and unit mappings are auto-detected when a connection is activated.

Action Notifications

When your partner acts on a mirrored document, you are notified — and approval-level actions wait for you:

• Accept, reject, confirm — you receive a notification, and an approval banner appears on your document. Choose Approve to apply the matching status change (accepted, rejected, or confirmed), or Dismiss to clear the notification without changing anything.
• Ship, deliver, revision request — informational notifications only; no approval needed.

Your document's status never changes without your explicit approval.

Webhooks

For event-driven integration with external systems, each connection can register webhook endpoints subscribed to events such as connection.created, connection.accepted, connection.revoked, document.created, document.updated, document.synced, sync.completed, and sync.failed.

Webhook requests are signed with HMAC-SHA256 via the X-Gloyd-Signature header in the format t=<timestamp>,v1=<signature>, with a 5-minute timestamp tolerance. Failed deliveries are retried up to 5 times with exponential backoff; endpoints that keep failing are automatically disabled.