FluwConnect Business.ru data to a catalog in Fluw
Business.ru is available for projects in Russian Fluw accounts. Your team keeps products in Business.ru while the site shows buyers approved fields. Contact us to check availability for your account and agree on permissions and updates.
Before you connect
Your inventory stays in Business.ru
Business.ru is a cloud system for inventory, sales and customer management. Connect the account your team already uses to a Fluw project, then choose which data the website needs.
- 1
Open Fluw in the Business.ru app marketplace.
- 2
Select the Fluw project to connect.
- 3
Confirm access in Business.ru and return to Fluw.
- 4
Check the connection status and test a few product records.
From a source record to a product page
Demonstration using test data
| Source field | Example value | On the website |
|---|---|---|
| Name | Essential cotton T-shirt | Product title |
| SKU | TS-NV-M | SKU |
| Color | Navy blue | Color option |
| Size | M | Size option |
| Price | $19 · demo | Displayed price |
| Stock | 42 units · demo | Availability |
Read access to the agreed catalog data only
This diagram shows the base read-only flow. Writing orders, changing products in Business.ru, and other reverse actions are not automatically included.
Essential cotton T-shirt
100% cotton · navy blue · size M
A buyer chooses. Sales receives the context.
- Essential cotton T-shirt · M · navy blue · quantity 2
- New York
- Confirm delivery date
The request destination is configured for each project
The connection goes through four verifiable stages
Each stage has a concrete output: data scope, minimum permissions, a test mapping, and acceptance criteria.
- 01Agree the fields
Define the scope
List the products, groups, images, prices, stock, and attributes the website actually needs.
- 02Check permissions
Grant minimum access
The base flow needs read access to the agreed catalog data. Write-back is not assumed automatically.
- 03Review the sample
Map and test
Compare IDs, names, specifications, images, and commercial fields using a test sample.
- 04Record acceptance
Accept the result
Review cards, update frequency, outage behavior, and the sales-request contents against the agreed checklist.
What the base connection reads and what is agreed separately
An integration is not a promise of instant synchronization. Its mode depends on the API, permissions, and data requirements of each company.
The base scenario reads catalog data
Fluw uses approved fields for product cards and filters. Changing Business.ru products or sending requests back to the source requires a separate agreement.
- Read: products, groups, images, descriptions, prices, stock, and attributes—only in the agreed scope
- Permissions: minimum read access to the required catalog data
- Write-back: not included in the base flow and assessed separately
- Frequency: agreed from source capabilities and website needs, without an instant-update promise
- Source outage: use the last-confirmed value, hide the status, or send the buyer to sales
- Acceptance: test records match the source, empty fields are handled, and requests contain selected products
Operating behavior is agreed for each project
Frequency depends on Business.ru capabilities and website requirements. Separately, decide what buyers see when fresh data is temporarily unavailable.
- Update frequency
- Configuration defines the update interval or event, acceptable delay, and how to show the last-confirmed time. Instant synchronization is not promised by default.
- If Business.ru is unavailable
- Show the last-confirmed value with a date, hide price or stock, or route the buyer to sales. Select one behavior before acceptance.
Business.ru connection questions
Which data can be connected?
The set depends on the API and permissions. We define the required fields first, such as products, images, prices, stock, and attributes.
How often will prices and stock update?
The frequency is set by the source and integration configuration. We do not assume instant updates and agree on the mode before launch.
What happens if Business.ru is temporarily unavailable?
We choose a fallback in advance: show the last confirmed value, hide the status, or route the buyer to a manager request. The right choice depends on the process.
Does Fluw get permission to change data in Business.ru?
Not unless that workflow is agreed separately. In the base example, Fluw reads approved data and presents it on the site.
How is the connection accepted?
Using an agreed sample, verify IDs, fields, empty values, price, and stock. Then check the selected update frequency, source-outage behavior, and the contents of the sales request.
Describe the catalog and what buyers should be able to do
List the fields to read from Business.ru, the required update behavior, and what sales should receive.