SAP Commerce - Hybris and BSeller integration

Connect SAP Commerce - Hybris and BSeller for orders, products, inventory, pricing, and customer records — tax invoices and receivables in the ERP, fulfillment updates on the e-commerce side.

Contact

Workflows / SAP Commerce - Hybris and BSellerExample

SAP Commerce - HybrisE-commerce

BSellerERP

Illustrative example. The direction of each record is defined on the project.

Fully managed or self-serveFully managed or self-serve

Specialist team, depending on the plan

400+ connectors; others on demand, after an API and connectivity check

Included workflows, configurable.

A ready starting point. Each workflow is adjusted to the rules of your operation.

Adjustments by our team or yours, in the low-code builder.

Workflow	Direction	What can be configured
Catalog	From the ERP to e-commerce.	Fields, field mapping, filters, and schedule
Inventory	From the ERP to e-commerce.	Warehouse, balance rule, and frequency
Pricing	From the ERP to e-commerce.	Price list, channels, and update rules
Order	From e-commerce to the ERP.	Trigger, filters, and mapping in the ERP
Customer record	From e-commerce to the ERP.	Fields, match key, and create or update
Status	From the ERP to e-commerce, and from e-commerce to the ERP.	Field mapping of states and the events that start a run
Tax invoice	From the ERP to e-commerce.	Tax data on the channel and when it returns

How data moves.

SAP Commerce - HybrisE-commerce

orders

customer records

products · inventory · pricing

tax invoice and tracking

Flouiworkflows and runs

orders

customer records

products · inventory · pricing

tax invoice and tracking

BSellerERP

Exemplo ilustrativo.

Fully managed or self-serve.

Fully managed

Our team implements, runs, and maintains the integration.

Mapping and implementation by specialists
Adjustments when E-commerce or ERP changes
Your team stays on the business

Self-serve

Your team uses the platform. Specialists step in when you need them.

Low-code workflow editor
Execution history
Your own connectors and entities for developers

From the first conversation to operation.

01First conversationSystems, volume, and scope.
02MappingWorkflows, business rules, and responsibilities.
03ImplementationConfiguration, tests, and validation.
04OperationFollow-up on the model you chose.

Similar integrations.

Same kind of integration.

FAQ

Which records usually move between e-commerce and the ERP?

In general: orders, products, inventory, pricing, and customer records. Tax invoices (Brazil’s NF-e), receivables, and fulfillment updates are often part of the mapping, depending on what each system exposes. What actually runs depends on the project mapping and an API and connectivity check on each system.

Does Floui issue the tax invoice?

No. Floui does not issue the tax invoice (Brazil’s NF-e). Issuing stays in the ERP, or in the tax system in your stack. Status and tax-invoice data move only when those systems expose them, and only after a connectivity check on the project.

Does the e-commerce order become a sales order in the ERP?

That is the usual path when e-commerce and the ERP allow the mapping: an order on the channel can create a sales order in the ERP. Triggers, filters, and field mapping are set per project — by our team or yours, in the low-code builder — after an API and connectivity check on both systems.

Can workflows follow our business rules?

Yes. Workflows are the starting point: filters, field mapping, and business rules are adjustable. Depending on the plan, this can be fully managed by the specialist team, or your team can work self-serve on the platform.

Related integrations

Let's connect SAP Commerce - Hybris and BSeller.

A specialist in e-commerce integration will talk with you.