What is Easyitem Sync?

Easyitem Sync makes your modules talk to each other: an event in one triggers an action in another.

Modules communicate through events — one announces what happened, the other reacts. A warehouse worker closes a pick in WMS and OMS knows, in a fraction of a second, that the order is only waiting for the courier. Nobody clicks anything.

This is not a separate tool or a separate screen. Sync works through the same automated actions you already set up in OMS. Triggers shared by other modules sit in the same list as local ones.

You do not need every module. Automation works inside OMS from day one. When you add another module, rules start working between them — without rebuilding what you already have.

Sync works both ways: listening and acting

It is easy to think this is only about triggers — a module hearing what happened elsewhere. That is half the story. The other half is actions that reach into another module.

1. Listening — triggers from another module. A rule in one module reacts to an event in another. WMS, for example, has OMS and PIM trigger groups, and OmniChannel has the Product added in PIM trigger.

2. Acting — a rule reaches into another module. The action list includes ones that do something outside their own module:

• Fetch product information from PIM (in WMS) — a warehouse rule reaching for product data.
• Update product information from PIM (in WMS) — refreshing data with no manual export.
• Fetch an order from OMS (in WMS) — the warehouse taking an order for processing by itself.

3. Custom events as a bridge. The Fire a custom event action (OMS, PIM) and Fire a custom trigger (WMS) let you build a sequence where one rule ends with a signal and another rule picks it up. That is how you join steps no built-in action connects.

So when designing a rule, ask two questions: what should it react to and where should it run. The answers do not have to point at the same module.

What exactly works thanks to Sync

The following are not features of a single module — they exist because the modules can see each other's events. With only one module you simply will not see them.

• Product data — PIM is the source OmniChannel builds an offer from, and the one WMS fetches and refreshes product information from.
• Stock levels — WMS is the source of the stock OmniChannel sends to the platforms; signals about a stock threshold and a shortage during picking set off a reaction on the sales side.
• Orders — the warehouse sees that an order was created in the orders module and can take it for processing and plan the pick by itself.

How to spot it in the panel — two things:

• A SYNC marker next to a trigger on the rule list means that trigger takes part in Sync — it is either shared with other modules or arrives from one. This includes local triggers: "Product added" in PIM carries SYNC, because WMS and OmniChannel listen to that event.
• A group named after a module in the trigger dropdown — the PIM group inside WMS, for example, or OMS inside PIM. Those are triggers arriving from that module.

In other words: the group tells you where an event comes from, and the SYNC marker tells you it takes part in communication between modules. The website puts it briefly: Sync shares selected triggers from one module with the others.

Sync is included. There is no separate subscription and no charge for the number of rules, triggers or events. It works the same way on the free plan and on paid plans.