CUSTOMER STORY · MULTICHANNEL SALES
RichSoda helped OCBT implement Odoo and connect Shopee, its own shopping app, and Taiwan e-invoicing. The project also moved key order operations into background processing and adapted the sales order interface for the customer service team's day-to-day work.
One sales workflow for several ways of taking orders
OCBT receives orders through Shopee and its own shopping app. Its customer service team also takes orders through Facebook, Instagram, and TikTok private messages. These channels need to feed into a workable sales process without requiring every channel to operate in the same way.
RichSoda connected the two online sales channels so their orders import into Odoo automatically. Social-message orders remain a customer service workflow: staff take the order and work with an adapted sales order interface. This is distinct from automatically importing private messages.
Connecting Shopee, the shopping app, and e-invoicing
- Shopee: automatically import store orders into Odoo.
- OCBT's shopping app: automatically import app orders into the same Odoo sales workflow.
- E-invoicing: connect Taiwan electronic invoicing as part of the implementation.
With online orders brought into Odoo, the team can handle them in one ERP workflow instead of re-entering each order from the storefront or app. The e-invoicing integration connects another part of the order-processing flow.
Moving time-consuming operations into the background
When many orders arrive close together, order processing can concentrate work into a short period. RichSoda customized sales order confirmation, invoice processing, and transfer validation to run asynchronously in the background, helping reduce peak load and the time users spend waiting on the screen.
- Sales order confirmation: process the confirmation operation in the background.
- Invoicing: move invoice processing out of the user's foreground interaction.
- Transfer validation: process picking validation in the background as well.
This is a customization delivered for OCBT, not a claim that every Odoo installation processes these actions asynchronously by default. Background processing also does not mean instant completion: the underlying operation still needs to finish before its result is complete.
The goal is to keep the user's interaction from waiting on every processing step while reducing concentrated processing load.
A sales order interface that fits customer service
Customer service staff may be taking an order while speaking with a customer through a Facebook, Instagram, or TikTok private message. RichSoda adjusted the Odoo sales order page to better fit this order-taking workflow, rather than asking the team to work around an unchanged interface.
The online integrations and the interface changes address different needs: Shopee and app orders arrive automatically, while the adapted sales order page supports orders handled by people. Both workflows use Odoo as the ERP platform.
What this changes for daily operations
The implementation brings together channel integration, processing behavior, and the user's working interface. Online orders can enter Odoo automatically, key operations can run in the background, and customer service staff have a sales order page better suited to social-message orders.
For a similar project, start by distinguishing automatically imported orders from staff-entered orders, then identify which processing steps cause users to wait. Plan the integrations, background work, and interface changes around those actual workflows.
Discuss your sales channels and order workflows with RichSoda