Connects to the catalog you already run.
Salla, Zid, Shopify, WooCommerce, feed and API integrations
Hephon Commerce reads your products, prices and stock from the platform you use today, branch by branch, and sends orders back where your team already works.
- ShopifyProducts and variants, kept current by webhooks.
- WooCommerceProducts and variations, kept current by webhooks.
- APISallaProducts, variants and stock per branch, in Arabic and English.
- APIZidProducts, variants and stock per location, in Arabic and English.
- Google product feedJSON lines with Google Merchant fields, from a URL or an upload.
- APIPush APIYour systems send products, prices and stock per branch.
- APIYour platformA connector to your platform's API, built by our team.
In short
Hephon Commerce connects to a retailer's catalog through Shopify, WooCommerce, a product feed in JSON lines with Google Merchant fields, a REST API, or a custom connector built for the retailer's own platform. Prices and stock are kept per branch, and refreshes run in the background on a schedule.
Orders go to the retailer's own checkout in its app, to its platform or server through an API, or to its team as an order ticket. Developers get scoped API keys, idempotent writes and signed webhooks.
Updated
Catalog in, orders out.
One assistant between your systems and your shoppers, on every channel.
Your catalog
- Shopify
- WooCommerce
- Product feed
- Your API
Hephon assistant
Your rules, your languages
- 1Understands
- 2Searches
- 3Checks
- 4Fills the basket
Your shoppers
- Your app
- Phone calls
Which platforms and feeds can it read?
Shopify
Products and their variants are read through Shopify's Admin API. Each variant becomes a product the assistant can add, because a variant is what a basket holds. Shopify's product webhooks start a change pull when a product is created or edited, and the full refresh removes products you deleted.
Salla
The store installs the Hephon app from Salla, and its access arrives on its own. Each Salla branch becomes a store with its own stock, products are read in Arabic and English with every option as an item the assistant can add, and categories and barcodes come with them. Salla's product and category webhooks start a refresh, and tokens are renewed before they expire. Ordering can be turned on for pickup: the assistant places an unpaid order at the shopper's branch and sends Salla's payment link.
Zid
The store approves the Hephon app in Zid. Each Zid location becomes a store with its own stock, names come in Arabic and English, and variants and nested categories are kept. Hephon subscribes to the store's product webhooks so edits start a refresh. Ordering can be turned on for delivery: the assistant creates the order with Zid's payment link for the shopper to pay.
WooCommerce
Products and variations are read through the WooCommerce REST API with a consumer key. You paste a webhook secret we issue into WooCommerce, and each product update it sends starts a change pull.
Product feeds
A file in JSON lines, one product per line with the field names of a Google Merchant feed: id, title, price, sale price, availability, brand, GTIN and image links. It can sit at an https address we read on your schedule, or be uploaded through the API (up to 50 MB, compressed or not). A line can name the branch it prices, so one feed can carry every branch.
REST API
Your systems send products in batches of up to 500, update the price and stock of one branch, or stop selling a product. Every import returns a run you can follow until it is done.
Custom connectors
Retailers with their own ordering platforms get a connector built by our team to that platform's API. It reads branches, products, prices and stock, and can place orders when the platform allows it.
Your catalog, ready to be asked.
Connecting is the start. Every product is prepared so shoppers can find it however they ask.
- Per-branch data
- Each branch keeps its own prices and stock, and the assistant answers from the shopper's branch.
- Refreshed on a schedule
- Catalog refreshes run in the background on the schedule you set, never in the way of a shopper.
- Understood, not just copied
- Every product gets search names in each language your shoppers use, so “7aleeb” finds milk.
How does catalog syncing work?
Each source has its own schedule: a full refresh hourly, every six hours, daily or weekly, and change pulls as often as every 15 minutes. Refreshes run in a background worker, never inside a shopper's request, so a large import does not slow anyone's chat. After products come in, new and changed ones are prepared for search: they get search names in each language your shoppers use, and are checked against your content rules. The source's page shows every run, how many products changed, and each request it made to your platform.
How are prices and stock handled per branch?
Every branch is a store with its own country, currency and timezone, and each product has its own price and stock in each branch. The shopper sees what their branch can deliver, in its currency. A Shopify or WooCommerce shop comes in as one store; retailers with branch-level prices send them through a feed, the API or a custom connector.
Where do orders go?
Inside your app or website, the assistant hands the basket to your own checkout, and your platform takes the order as it does today. Your platform can report those orders through the API, so you see which ones the assistant helped with.
On WhatsApp and phone calls, where the order is placed through Hephon Commerce once the shopper confirms, there are three ways. Your platform's API, through a connector that supports ordering. Your own server, through our Orders API, which your developers implement. Or an order ticket your team handles in the Orders screen. Every placement carries an idempotency key, so a retry never places an order twice.
What does the API offer developers?
A REST API under /v1 with an OpenAPI description. Keys are scoped (catalog, orders, sessions, shopper data and more), every write accepts an Idempotency-Key header, and errors come back in the standard problem format. Your backend can open a shopper session, read a conversation and its basket, report orders and delete a shopper's data. Webhooks send basket changes, checkout requests, hand-overs to a person, staff replies, order events and completed deletions. Each delivery is signed, timestamped and retried with growing waits.
What it does not do
- The Shopify and WooCommerce connectors read your catalog. They do not place orders in those stores today: WhatsApp and phone orders arrive as order tickets or through the Orders API.
- Feeds are read in JSON lines. An XML or spreadsheet feed needs converting first.
- Stock is as fresh as your last refresh or API update. It does not read your stock live during each chat.
When Hephon Commerce is not the right fit
- You have no online catalog with prices and stock, and no way to export one.
- You need an integration on day one with a platform we have no connector for, and cannot produce a feed.
An API built for retail.
Documented and predictable, for the teams who run your platform.
- REST API
- Catalog, conversations and orders over HTTPS, with errors in a standard problem format.
- Scoped API keys
- Each key can do only what it is for, and every write accepts an Idempotency-Key.
- Signed webhooks
- Order, basket and conversation events delivered to your server, signed and retried.
- Orders your way
- Your platform's API, our Orders API on your server, or order tickets for your team.
Live in three steps.
- 1
Pick your source
Salla, Zid, Shopify, WooCommerce, a product feed, the API, or a connector we build for your platform. Credentials are encrypted when you save them.
- 2
Run the first import
Products, prices and stock come in branch by branch, and each product is prepared for search. You see every run and every request on the source's page.
- 3
Set the schedule and orders
Choose how often it refreshes and where orders go, then test the assistant on your own catalog.
Integrations, answered.
See it on your own catalog.
We set up a demo with your products, your branches and your shoppers' languages.
