Installation and setup

Requirements

• CS-Cart and Multi-Vendor 4.17.2 or later.
• Administrator access to the store’s admin panel.
• A seller account at OTTO Market with access to OTTO Partner Connect (OPC), and the user right API-Zugriff (API access) for the user who creates the credentials. You use your own account: you do not need to register as a service partner (see “How OTTO access works” below).
• A cron job on your server (see step 8).

How OTTO access works (read this once)

OTTO Market knows two kinds of API users (source: api.otto.market/docs, “API Integration for Sellers” and “API Integration for Service Partners”):

	Seller (your own app)	Service partner (public or private partner app)
Who	A merchant connecting their own OTTO Market account	A software company that serves many sellers
Registration	None beyond your seller account	Free registration at servicepartner.otto.market/register, then permissions in OPC: Sandbox Apps (30 days of testing, unlimited after a self-disclosure form), Private Production Apps, and for public apps a pilot, quality checks per scope and an OTTO Market training (Public Production Apps)
Credentials	You create an app in OPC (API-Zugriff) and get a Client ID and Client secret	OAuth2 authorization code flow for the installation, then a developer token and an installation access token per seller
Token	POST /v1/token, grant_type=client_credentials	POST /v1/apps/{appId}/installations/{installationId}/accessToken

This add-on implements the seller path: every store owner (or, in Multi-Vendor, every vendor) enters the Client ID and Client secret of an app they created in their own OPC account. No OTTO data goes through Kavio Labs. The add-on is therefore not an OTTO “public app” and does not require a partner registration to use.

Create the OTTO credentials

1. Log in to OPC (portal.otto.market). If the section is missing, give your user the right API-Zugriff in the user administration and log in again.
2. Open API-Zugriff. It lists a Sandbox and a Live environment (separate apps for each).
3. Choose the environment and click Neue App erstellen (create new app). Enter an app name and select the scopes products, availability, orders, shipments, returns, shipping-profiles. Click App erstellen.
4. The credentials tab opens. Copy the Client ID and the Client secret right away: the secret is shown only once (if you lose it, rotate it in OPC).
5. Create a shipping profile in OPC if you do not have one (it defines the processing and transport time every product uses).

Whether your seller account has sandbox access, and how many apps you may create, is decided by OTTO. If there is no Sandbox section for your account, start in Live mode with a single test product.

Install the add-on

1. Download the kv_otto_market-<version>.zip package from your Kavio Labs or CS-Cart Marketplace account.
2. In the admin panel, open Add-ons > Manage add-ons.
3. Click the gear button and choose Manual installation, then upload the archive.
4. Find OTTO Market Connector in the list and make sure its status is Active.
5. Enter your license key under Settings > License (Kavio Labs downloads) and click Check now.

Connect OTTO

1. Open Orders > OTTO Market (the add-on page) and the Connection tab.
2. Choose Test mode and enter the sandbox Client ID and Client secret. Fill in the ship-from city and ZIP code (OTTO requires them for every shipment). Save and click Test connection: a green message (“Connected to OTTO Market (sandbox): n shipping profile(s)”) means the credentials and the scopes work.
3. Optionally enter the shipping profile ID (otherwise the first profile of your account is used), the return carrier (DHL, GLS or Hermes) and the product safety contact (GPSR).
4. Switch to Live mode and enter the live credentials only after a successful test; test again.
5. Map your categories on Categories (OTTO category names, resolved from OTTO’s category list) and the required attributes on Attributes, then map products on Listings (see Usage).
6. Choose the order statuses that start the work (see Configuration).
7. OTTO has no push notifications in its public API: new orders and returns are pulled by the cron job.
8. Add the cron job from the settings page (Cron section), every minute is fine. Overlapping runs are prevented.

Multi-Vendor

By default the marketplace owner connects one account for all vendors (Marketplace owner mode on). Switch it off to let each vendor connect their own OTTO account (their own OPC app) in the vendor panel (Connection tab).

Update

1. Upload the new package the same way. Your settings, credentials and data are kept.
2. The add-on adds missing tables and settings by itself on the first request after the update.

See CHANGELOG for what changed in each version.

Uninstall

Open Add-ons > Manage add-ons, click the add-on’s gear button and choose Uninstall. This removes the add-on’s settings, language variables and database tables, including the stored credentials. Products stay on OTTO; remove them in OPC if you no longer want to sell them.