By Artem Korsakov ·
Integrating a flower shop website with inventory management starts by defining bouquet availability, composition, and substitution rules. The website sells bouquets, while the accounting system stores individual flowers, packaging, and ready-made compositions. Before ordering integration, you must determine which data will reliably allow order processing. A simple match of product names does not solve this task.
Separate the Finished Product from the Bouquet Composition
A ready-made composition can be tracked as a separate item with available quantity. If the bouquet is assembled to order, its availability depends on components and assembly rules. Automatic exchange of one flower's stock does not yet show whether a specific composition can be fulfilled.
Consider a hypothetical shop: some products are on the ready-made display, others are assembled after confirmation. For the first group, the website can receive quantities of ready positions. For the second, a separate verification procedure or agreed calculation logic is needed. Combining both scenarios with one "in stock" marker is risky for the processing workflow.
Assign a Source for Each Data Type
Determine where names, prices, descriptions, and availability are changed. It is not necessary to store everything in one system, but for each field, the primary source must be clear. If a price is changed both on the website and in accounting, the next exchange might cancel manual edits.
Stable product identifiers and variants are required. Systems distinguish records by these IDs during renaming. Hypothetical bouquet sizes must be mapped explicitly: a matching label does not guarantee that it is the same item in two databases.
Describe update frequency and acceptable latency. The word "automatically" does not mean continuous synchronization. Between updates, the product might be sold through another channel. Therefore, it is necessary to separately define when availability is rechecked and how an employee learns about a conflict.
Order Submission Includes More Than the Cart
The following can be transmitted to accounting or a working system:
- items, variants, and quantities;
- fulfillment cost;
- buyer and recipient details;
- time interval;
- card text.
The composition depends on where employees fulfill the order. If an important field remains only on the website, staff will have to cross-reference two systems.
Agree on statuses. "Request received," "composition confirmed," "awaiting payment," and "order completed" are different events. Not all statuses need to be exchanged, but their meaning must match for employees and in the customer interface.
Errors Are Part of Integration
If one system is unavailable, data may not be sent immediately. An exchange log, clear notification to the responsible person, and an agreed method for retransmission are required. Retries must not create a second independent order instead of restoring the first.
In a hypothetical situation, the website accepted an inquiry, but the accounting system did not respond. The shop needs to see the saved request and understand that transmission is not yet complete. If the user has already paid, this status is especially important to separate from the fact of successful exchange.
Support after changes must be discussed separately. Updating an external service or data structure may affect the connection. Agreements should name who is responsible for diagnostics and the boundaries of included fixes. Promises of eternal functionality are insufficient here.
How to Prepare the Task and Accept Results
Gather system names, information about available connections, product samples, and several orders with exceptions. Start with a limited volume: for example, agreed exchange of a selected group of items and transmission of new orders. Further expansion should be evaluated separately. General rules for data transfer between systems are discussed in the article "How much does integrating a website with CRM or accounting system cost".
During verification:
- Change the price.
- Disable a variant.
- Send a repeated order.
- Reproduce a temporary error.
Compare information on both sides of the exchange. Check not only the presence of a record but also its composition, total, status, and subsequent handling by an employee.
At trike_dev, you can discuss a flower shop and integration separately, starting with describing data exchange and the actual order fulfillment process.
Frequently Asked Questions
Is stock counting per stem necessary from the start?
Only if it is reliably maintained and needed for the chosen scenario. Automation does not fix missing data. Sometimes honest confirmation by a manager is more useful than displaying inaccurate quantities.
What to do with order changes after submission?
Possibilities include transmitting a new version, manual editing in the main system, or separate agreement. The main thing is that old contents are not restored by the next exchange, and the employee sees the current version.
Can this work be estimated by the name of the accounting system alone?
Only preliminarily, while version, access rights, and required actions are unknown.