ikas
For ikas stores, products come from the Google Merchant catalog link as a data feed; for orders and customers your integrator sets up a push through the Data API. A direct ikas connector does not exist yet.
The steps and verification flags below are taken one-to-one from the preset the product shows in the setup wizard. A step or fact marked Not verified in the docs could not be confirmed in the platform’s public documentation; check it in your admin panel.
- Summary
- Products from the Google Merchant XML; orders via the Data API.
- Recommended path
- XML-CSV link (data feed)
- Available paths
- XML-CSV link (data feed) · Push via API (Data API) · Manual upload
- Researched
2026-09-26
What is verified
Each fact below was either confirmed in the platform's public documentation or not. Unverified facts are still usable, but check them in the preview before relying on them.
- ✓ Verified in the docs API
- ✓ Verified in the docs authentication
- ✓ Verified in the docs file format
- ✓ Verified in the docs admin menu paths
- ✓ Verified in the docs order statuses
- ✓ Verified in the docs webhooks
- ! Not verified in the docs feed URL
- ! Not verified in the docs record path
- ! Not verified in the docs field names
XML-CSV link (data feed)recommended
- In the ikas admin open Sales Channel → Add-ons → Google Merchant Center.
- Copy the .xml address in the 'Google Merchant Center catalog link' field and paste it in the wizard; the format is preset to Google Merchant.
- Orders and customers don't come through XML: also set up 'Push via API'.
Push via API (Data API)
- In the ikas admin create a private app with read_orders and read_customers scopes via Apps → My Apps → More → Create Private App (the client secret is shown once).
- Your developer or integrator reads orders from the ikas Admin API (GraphQL, listOrder) — with status (orderPackageStatus), tracking (orderPackages.trackingInfo) and customer phone — and sends them to the Zitena Data API.
- Create the secret API key in the wizard (or Settings → API keys) and share it with your developer or integrator over a secure channel.
- The ikas integration sends products to PUT /api/v1/catalog/products, orders to PUT /api/v1/orders and customers to PUT /api/v1/musteriler (examples on the Data API page).
- If orders include status, carrier, tracking number and the customer phone, the assistant recognises callers by phone and answers shipping questions.
Manual upload
- Export the product list as CSV or XML from your platform's admin panel.
- Upload the file in the wizard; columns are mapped automatically and you can adjust them.
- A manual upload is one-off: re-upload when prices or stock change, or switch to an XML link.
Feed template
Product feed (Google Merchant catalog link)
- Format
google_merchant✓ Verified in the docs- URL pattern
- Not documented — copy the address from the admin panel.
- Known field names
item_ref←g:id,id,g:item_group_idurun_kodu←g:mpn,g:gtin,sku
Known field names are only applied when they actually exist in your file; an unmatched name does nothing. The mapping is always shown in the preview before anything is imported.
Order status mapping
Status values from the platform are mapped to standard short names, and then to your own status in the same group if you have one. Unknown values are left unmapped and flagged for you.
| Platform value | Standard short name |
|---|---|
CREATED | processing |
DRAFT | pending |
WAITING_UPSELL_ACTION | pending |
UNFULFILLED | processing |
READY_FOR_SHIPMENT | processing |
PARTIALLY_READY_FOR_SHIPMENT | processing |
PARTIALLY_FULFILLED | shipped |
FULFILLED | shipped |
READY_FOR_PICK_UP | shipped |
PARTIALLY_DELIVERED | shipped |
UNABLE_TO_DELIVER | shipped |
DELIVERED | delivered |
CANCELLED | cancelled |
REFUNDED | refunded |
WAITING | pending |
PAID | processing |
FAILED | failed |
Notes
The ikas Admin API is documented and uses client credentials (4-hour token); a direct ikas connector is the next step. The catalog link's URL pattern isn't documented: copy it from the admin.
Platform documentation
© 2026 Erusoft