What happens if the iikoWeb password changes?

Runs start failing, because Renta signs in with the stored login and password on every run. Open the connection in **Sources** and update the **Login** and **Password** fields, and the pipelines built on it resume.

Why did my run fail because of the start date?

IikoWeb pipelines refuse a start date more than 89 days in the past. The run stops before any report is ordered. Move **Date start** back inside the window. If the pipeline is incremental, the history that earlier runs loaded stays in the table.

Can one pipeline cover several organisations?

Yes. **Organisation** is a multi-select, and every organisation you tick lands in the same table. Add a field such as Store.Name or Department to tell the rows apart.

Where does the order_created_date column come from?

Renta fills it from the order open time, the OpenTime field of the same row. Select OpenTime together with order_created_date . The column matters because it is the partition key that makes incremental loading possible.

Why do the column names differ from the field names in the picker?

Dots are not allowed in warehouse column names, so Renta replaces them with underscores. The field OpenDate.Typed becomes the column OpenDate_Typed , and Store.Name becomes Store_Name .

Why does a run take so long?

IikoWeb builds a separate report for every day of the range and every selected organisation, and Renta waits for each report to be ready. A wide date range multiplied by several organisations adds up. Shorten the range or split organisations across pipelines if you need the data faster.

IikoWeb

Renta exports two OLAP reports from your iikoWeb server to your data warehouse: dish-level sales and stock and accounting transactions.

A row of Sales report is one dish in one order, with its money and quantity figures. A row of Transactions report is one stock or accounting entry.

Authentication

Renta connects to iikoWeb with the address of your server and a user's login and password. It signs in with these credentials at the start of every run, requests the reports, and closes the session when the run finishes.

Renta checks the credentials when you save the connection, so a typo in any of the three fields surfaces immediately.

Your credentials are encrypted in transit and at rest. To cut Renta off, change the user's password in iikoWeb or disable that user.

Connect IikoWeb as a source

Go to the CatalogStep 1

In the Renta console, open Connections > Catalog in the left sidebar.
Expand the CRM category and click the IikoWeb card. The neighbouring IikoCloud card is a different connector for the iikoCloud delivery API.

IikoWeb card in the CRM category of the Renta connection catalog

Enter the server address and credentialsStep 2

Fill in the three fields of the form:

Hostname.
The address of your iikoWeb server, such as company.iikoweb.ru, without https://.
Login.
The iikoWeb user Renta signs in as.
Password.
The password of that user.

Hostname, Login and Password fields on the Add a new IikoWeb connection page

Name the connection and saveStep 3

In Source name, give the connection a label. It is used only inside the Renta console. Click Save, and Renta signs in to your server to verify the credentials.

Source name field and the Save button on the IikoWeb connection form

Verify the connectionStep 4

The new connection shows up in Sources with the Active status. Pipelines can now use it.

Sources list with the new IikoWeb connection in the Active status

Create an IikoWeb pipeline

Select IikoWeb as the sourceStep 1

In the left sidebar, click New pipeline. Keep the ETL tab selected, find IikoWeb under Already connected, and click Next step.

Select a source step of the pipeline wizard with IikoWeb under Already connected

Select the connectionStep 2

Choose the IikoWeb connection you created and click Next step. The card shows the login and the server host behind it.

Select your IikoWeb connection step with the server host shown on the card

Select a destinationStep 3

On the Destination step, pick the warehouse that receives the data and click Next step.

Select a destination step with Google BigQuery among the connected warehouses

Select the destination connectionStep 4

Choose the destination connection and click Next step.

Select your Google BigQuery connection step with the dataset and project on the card

Pipeline configuration

All settings of an IikoWeb pipeline live on the last step of the wizard, one scrolling form.

Organisation

The organisation picker decides which parts of your iiko account the pipeline covers.

The picker lists the organisations of your iikoWeb server together with their numeric identifiers. You can tick several. Renta loads them one after another, and all their rows land in the same table.

Report type

One pipeline loads one report type.

Report type	Description
`Sales report`	Sales broken down to a dish within an order: dish, order, department, store, cash register and payment attributes, plus money and quantity figures (cost price, discounts, VAT, profit, dish counts).
`Transactions report`	Stock and accounting entries: product with its hierarchy and tags, store, account and contra-account, document, transaction type, and the amount moved.

Parameters

Choose the iikoWeb fields to load. Each selected field becomes a column of the destination table.

Each report type has its own field list. It matches the columns of the same OLAP report in the iikoWeb interface. The Selected tab collects everything you ticked.

Dots in field names turn into underscores in the destination table, so OpenDate.Typed arrives as the column OpenDate_Typed.

In Sales report, the order_created_date field is filled from the order open time, OpenTime, so select the two together. It is also the partition key of the table, which makes incremental loading possible. See Sync strategy.

Integration and table name

Two names identify the pipeline: one in the Renta console and one in the warehouse.

Integration name and Table name fields in the IikoWeb pipeline settings

Integration name.
The display name of the pipeline in the Renta console.
Table name.
The table in your destination. Keep the generated name or type your own.

Date range

The date range bounds the history that the first run loads.

Date start.
The first day to load.
Date end.
The last one, either a fixed date or a moving boundary such as Today.

IikoWeb pipelines refuse a start date more than 89 days in the past. A run whose window begins earlier fails before any report is ordered, so keep Date start within that limit.

IikoWeb builds a report for every day of the range on its own side, organisation by organisation, and Renta waits for each report to be ready. A wide range across several organisations loads noticeably longer than a few days.

Overwrite period

The overwrite period defines how far back each scheduled run reloads days it has already loaded.

Sales figures for recent days keep moving while shifts are closed and orders are corrected in iiko. The overwrite window brings those corrections into the table: each run deletes its last days and loads them again. The default of Last 3 days covers a typical closing cycle.

Schedule

The schedule sets how often the pipeline runs. All times here are read in UTC.

Schedule type	Description
Manual	The pipeline runs only when triggered from the Renta console or through the API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time (the exact time each run starts), then click Create pipeline.

Update time dropdown and the Create pipeline button of an IikoWeb pipeline

Renta also supports API triggers and orchestrators such as Apache Airflow, Dagster, and Prefect. See the scheduling documentation for details.

The pipeline lands in the Pipelines section under the ETL tab, where you see its table name, run progress, and extracted row count.

Pipelines list with the new IikoWeb integration in the Completed status

Sync strategy

The table below describes how Renta synchronizes each IikoWeb report type.

Strategy	Supported report types	Description
Incremental	`Sales report` (with `order_created_date` selected)	The destination table is partitioned by `order_created_date`. Each run takes the days added since the previous run plus the overwrite window, drops those day partitions, and loads them again with the current figures.
Full reload	`Sales report` (without `order_created_date`), `Transactions report`	Without a date partition key every run replaces the whole table with the current date range.

Full reload and the 89-day cap together erase history: every run rewrites the table and can reach at most 89 days back, so anything older disappears on the next run. For Sales report, tick order_created_date if you plan to keep more than a quarter of sales.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.