The warehouse is Oplog, the operation is in Pixa. Every step from order to delivery runs from one panel.
Order handover.
An order from your channels is sent to Oplog if it matches the rule, and the Oplog reference is written to the order.
Stock sync.
Stock at Oplog is pulled every half hour, added to your central warehouse and sent to the channels by Pixa.
Shipping details.
When Oplog hands the parcel over, the carrier and tracking number come back to the order and are written to the channel.
Stock per warehouse.
Oplog, your central warehouse and any others are shown separately per product, while the channel sees the total.
Returns coming back.
A return approved on the channel is reported to Oplog, and stock is written there when the item arrives.
Warehouse priority.
Which warehouse fulfils which order is set by a rule, which can be defined per channel.
Oplog automations. Order, stock, shipping and return flows are set up in the panel, and Pixa runs them.
A live automation in three steps. Choose it. Configure it. Connect it.
Choose it from the list.
Prebuilt automations are chosen from a list; nothing is built from scratch.
Set the rule in one panel.
You choose the trigger, the condition and the timing on one screen, and the rule starts working for orders going to Oplog the moment you save it.
One channel, or all of them.
The same rule applies to Oplog alone or to every connected warehouse, and a new warehouse joins its scope automatically.
Your outsourced warehouse, connected.
Oplog, Fi Commerce, Hepsilojistik and Amazon Logistics (FBA), and any other fulfilment partner you work with, all through the same path.
All integrations →
Trust is built in. Defined permissions. Prebuilt setups. Traceable actions.
Role-based permissions.
Each user only sees and changes what they are authorised for.
Prebuilt setups.
Proven setups work from day one, with nothing to build from scratch.
Every action is logged.
Who made each change, when and why is on record.
Three details specific to Oplog. Product push, expiry dates, cancellations.
Products go to Oplog.
Pixa records are sent to Oplog by barcode and SKU, so you never create the product twice.
Expiry dates.
Batch and expiry dates are pulled from Oplog each night, and stock nearing expiry is flagged.
Cancellations and returns to Oplog.
An order cancelled on the channel is cancelled at Oplog too, and returns are reported there.
Oplog automations. The rule is yours, the steps are Pixa’s.
An order from your channels is sent to Oplog if it matches the rule, and the Oplog reference and status are written to the order.
How it works







Frequently asked
questions
Choose Oplog in the Market and enter your account details; the connection is tested and products are sent to Oplog by barcode and SKU.
Those matching the warehouse priority rule, which can be set per channel or per product; they are sent the moment they land.
Every half hour. It is added to your central warehouse stock and sent to the channels by Pixa.
Yes. When Oplog hands the parcel over, the carrier and tracking number come back to the order and are written to the channel.
Yes. Oplog, your central warehouse and any others are shown separately per product, while the channel sees the total.
Yes. An order cancelled on the channel is cancelled at Oplog too, and an approved return is reported there.
Yes. Batch and expiry dates are pulled from Oplog each night, and stock nearing expiry is flagged.
Yes. Fi Commerce and Hepsilojistik are ready connections, and several outsourced warehouses run in the same panel.






































































































