1. Business.ru record
- Name
- N-240 pump
- SKU
- N-240
- Price
- $480 · demo
- Stock
- 12 units · demo
Business.ru integration
Connect Business.ru data to a catalog in Fluw
Your team keeps products in Business.ru while the site shows buyers only approved fields. Before launch, we check permissions, the data contract, and the update mode.
2. Access and fields
Read access to the agreed catalog data only
- name → product name
- sku → SKU
- price → price
3. Website card
N-240 pump
SKU N-240 · demonstration price and stock
4. Sales request
- N-240 pump · quantity 2
- New York
- Confirm delivery date
The request destination is configured for each project
How the connection works
The connection goes through four verifiable stages
Each stage has a concrete output: data scope, minimum permissions, a test mapping, and acceptance criteria.
- 01
Define the scope
List the products, groups, images, prices, stock, and attributes the website actually needs.
Agree the fields - 02
Grant minimum access
The base flow needs read access to the agreed catalog data. Write-back is not assumed automatically.
Check permissions - 03
Map and test
Compare IDs, names, specifications, images, and commercial fields using a test sample.
Review the sample - 04
Accept the result
Review cards, update frequency, outage behavior, and the sales-request contents against the agreed checklist.
Record acceptance
Connection boundaries
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.
Open the catalog walkthroughRead: 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
Updates and source outages
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.
FAQ
Business.ru connection questions
Buying questions are part of the integration brief, not an afterthought.
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.
Start with the required fields
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.