Kiero OMS knowledge base.

Open Settings → Integrations → Add integration → PrestaShop. Each customer connects their own shop URL and Webservice key. Pilot enrollment and a Kiero module are not required. Connecting requires organization owner/admin access; publishing also requires product write permission. Demo organizations cannot connect.

Supported scope

Import orders in selected states, including customer, delivery/invoice addresses, lines, currency, amounts, taxes and payment evidence. Publish OMS products with descriptions, SKU/EAN, category, language, tax, images, prices, stock and combinations mapped to existing shop attributes. Optional price/stock synchronization applies only to products published by this connector; both switches start off.

Verified with PrestaShop 9.1.5. Other versions require qualification; publication needs PATCH. Full catalogue import, attribute creation, refunds, writing order states/tracking back, webhooks, currency conversion and shared/advanced stock are not supported.

1. Enable Webservice and create a key

1. In PrestaShop administration open Advanced Parameters → Webservice.
2. Set Enable PrestaShop's webservice → Yes and save. “This functionality has been disabled” usually means this global switch is off; enabling a key alone does not enable Webservice.
3. Select Add new webservice key, generate a 32-character key, describe it as “Kiero OMS”, enable it and assign the permissions below. Save.
4. Do not select “All”. PUT and DELETE are unnecessary.

Purpose	Resources	Methods
Connection and orders	shops, orders, customers, addresses, countries, currencies, carriers, order_states	GET
Automatic timezone discovery	configurations	GET; optional for order-only access
Products	products	GET, POST, PATCH
Images	images	GET, POST
Stock	stock_availables	GET, PATCH
Publication settings/dictionaries	configurations, languages, categories, shop_groups, currencies, tax_rule_groups, tax_rules, taxes	GET
Variants	combinations	GET, POST, PATCH
Variant attributes	product_options, product_option_values	GET

Paste the key only into Kiero's connection form. Never put it in URLs, messages, screenshots or product descriptions. It is stored encrypted server-side. If disclosed, generate a replacement, replace it in integration settings, test the connection, then disable the old key.

2. Check your hosting

Use a publicly reachable HTTPS shop URL such as https://your-shop.com or https://your-shop.com/shop/; a trailing /api/ is recognized automatically. No localhost, private IP, credentials/query/fragment in the URL or custom port. TLS must be valid.

Hosting must forward Authorization and support GET, plus POST/PATCH for publication. External Basic Auth protecting /api conflicts with the Webservice key. Ask hosting to keep PrestaShop key authentication on API while retaining storefront/admin protection; do not remove protection from the entire shop. Change CGI mode only according to the actual PHP hosting setup.

3. Connect in Kiero

1. Enter a connection name, shop URL and key. Load accessible shops and order states.
2. Select the correct shop; this is required when several are accessible. Publication does not support shared shop-group stock.
3. Explicitly select importable order states, excluding cancelled/refunded orders. Names depend on your shop; nothing is preselected.
4. Check the shop's actual IANA timezone, for example Europe/London. Enter it if configuration discovery cannot supply it. An incorrect timezone shifts the import window.
5. Select your organization's legal entity and import start date. The date begins at 00:00 UTC.
6. Review automatic order import and save. New connections default to automatic import; existing connections may remain manual. Saving does not immediately import orders. Run manual synchronization or wait for the schedule, normally about five minutes plus queue processing time.
7. Test the connection, run an import and inspect sample orders in Orders: addresses, lines, currency, delivery totals and payment state.

Changing URL/key invalidates discovery; reload shops and states. Reimport should not create duplicate orders or deduct stock twice. Fix incomplete import errors and retry. Payment confirmation depends on a paid shop state and sufficient actual paid amount; custom payment modules need separate verification.

4. Publish products

1. Prepare the OMS product name, unique SKU, optional valid EAN-13, description and public HTTPS image URLs. Up to 10 JPEG/PNG/WebP images, each at most 8 MiB.
2. In Products, select one product or up to 20, choose Publish → PrestaShop and the intended connection.
3. Select an existing shop language, category and verified tax group. Choose no tax explicitly when appropriate; complex regional rates are not guessed.
4. Enter gross prices in the shop currency and nonnegative whole quantities. Kiero converts gross to PrestaShop net; changing currency does not convert amounts.
5. For multiple variants map every variant to existing attribute values. Create missing attributes in PrestaShop first. Each variant needs a distinct option set with the same attribute groups.
6. Products default to inactive. Select activation only if they should become available after verification.
7. Submit, wait for the operation's success, then inspect the product in PrestaShop. Queue acceptance alone is not success.

Kiero creates an inactive product, completes combinations, images, stock and mappings, then optionally activates it. Negative combination price impact is valid when a variant costs less than the base. Repeating publication for the same product/connection reuses its existing operation. Its input snapshot is immutable: Retry does not change descriptions, categories or the submitted selection.

5. Price and stock synchronization

Enable prices and stock separately in integration settings. OMS product/variant values are the source; avoid another system writing the same fields concurrently. Verify one item first, including stock zero. Updates run through the scheduled queue, not immediately after an edit.

Only products published by this connector are managed, not the shop's entire pre-existing catalogue. Stock is an absolute quantity; variant prices become impacts relative to the base price. The generic single/bulk offer price/stock editor does not write PrestaShop: edit the OMS product and use integration synchronization. This schedule does not update descriptions, categories or images.

6. Troubleshooting

Symptom	Action
Webservice disabled	Enable/save the global Webservice switch and check key activation.
401 / 403	Check key, resource rights, Authorization forwarding and external Basic Auth/WAF with hosting.
Publication permissions error	Apply the GET/POST/PATCH table; variants also need combinations and attribute dictionaries.
Currency/tax mismatch	Use the shop currency and supported tax group; do not merely relabel a price.
Image unavailable	Open it without signing in; check HTTPS, format, size and hosting restrictions.
Shared/advanced stock	Use supported independent shop stock or review the inventory model; never pick an arbitrary stock record.
Failed operation	Correct the cause and retry; do not create another connection to bypass the failure.
Reconciliation required	Do not publish a copy. A response may have been lost after a successful write. Support must compare provider IDs and operation state. An uncertain image upload requires manual verification; Retry alone cannot resolve it.
Missing order	Check selected shop/states, start date, timezone, integration activation, subscription eligibility and queue outcome, then retry.

Contact Support with integration name, PrestaShop version, time, product/order/job IDs and a safe error message. Do not send the key.

7. Pause or disconnect

Disable automatic orders and price/stock synchronization to stop schedules. Pause the integration to prevent subsequent jobs from working; this does not undo completed work or a request already sent. Imported OMS data and provider products remain. Removing the connection does not delete PrestaShop products. Disable/delete the dedicated key in PrestaShop when retiring the connection.

The roadmap indicates feature availability. The controlled 9.1.5 verification ran on 27 October 2026; it does not qualify every store version or configuration.