Component «OneBox Network»

How OneBox Network works

OneBox Network allows to configure the data exchange with other OneBox. This tool allows to tie up your CRM/ERP system with CRM/ERP system of your partners (for example, suppliers) and share the information in real time.

How does an average buyer's work in any company look like?

He completes an order, sends it by email, modifies the order in the chain, receives the paperwork via email, sends it out for payment in CRM/ERP, once paid sends the receipt by email.

What does the other party's person do? Exactly the same thing.

He transfers everything from the account software (CRM/ERP) to the email, then data from the email goes back to the account software.

What does the OneBox Network offer instead:

• you have an order in your CRM, you can send it to supplier right out of your CRM;
• if supplier also has its box - the order gets to it automatically, with the right workflow, all the products created and everything is specified;
• the comments are synchronized between the processes;
• documents are synchronized;
• shipments from warehouses are synchronized (if the supplier has written product off the warehouse, you'll get the transaction for "admission" to your warehouse).

If you partner (supplier) does not have OneBox - he will get an "install OneBox and your order will get to your CRM automatically" link. The order itself will be present in the email as well.

It's just a small part of what the Network provides. You can exchange orders, documents, storages, finances, contacts between boxes.

It's already active and available in OS.

Imagine a big company with numerous branches in every city.

The following issues starting to occur:

• somebody's fixing/refining the processes and the work falls off for the whole country at once;
• somebody from the branch accidently got extra permission level and started to fix the whole client baseж
• servers fall under DDOS attack - and everything got dead;
• a big workload came from a couple of branches - and all the rest are suffering.

What Network allows instead:

• created a dedicated OneBox for every branch or branch group, which would be a physical stand-alone server (or virtual one);
• there would be administrators engaged, who would build their own processes according to their needs, own permissions etc;
• central box (or several) created to offload the required processes at the needed stages to;
• for example, central box sends "order" to the branch, it navigates from process to process there, and when it gets to the finish - central box receives the "successfully completed by the branch" response;
• there's no single point of failure, you can't make the whole network go down. It's a network of decentralized CRM/ERP-s;
• there's a need to make an edit to the process for all branches? Just fix it for one branch, verify and enroll the changes for all branches;
• there're 100 branches more required to be created? Just get an image of one box and deploy it for 100 more new boxes.

Horizontal scaling

Imagine the company, which gets about 500 000 orders per week, for example retail network of grocery stores or pharmacies.

500 000 orders hit the box per week.

To make all these work quickly - create a separate box for every region (group of stores), where all the data will be stored and payments processed, and also a couple of major boxes, where all the orders will arrive for statistics purposes, creation of funnels etc.

Therefore the Network allows to solve the technical problem about workload and failure-resistance through the horizontal scaling of the system.