Connecting eStack Instances #371

New Issue

2026-06-29T08:37:57Z

rob commented

2026-06-29 08:37:57 +00:00

@tim What do you think about some service that would allow a company like ZR or Cbus to connect eStack instances as dependent or shared locations? Goal would be to allow synchronization of new SKU data, images and automatic inventory movements for shipments.

Right now, to add shipment stock to the shops I have to:

Download the catalog from ZR warehouse instance (parent or main instance)
Copy product catalog and supplier data to the Bulk Upload form to bulk create SKUs.
Download the Shipment Invoice csv for a zeneroe.estack.com shipment
Open it in LibreOffice and copy the SKU column into the Supplier SKU column so I can upload (shop locations all use the same SKUs as the zeneroe.estack.com parent instance).
Go to Manage Supplier Invoices in the shop instances and upload the Shipment Invoice csv.
Go to QC and move the stock from QC to another location.

We do not need QC at the shops, so this step could be skipped. I think I created an issue to make QC optional overall, but that's not a priority. I assume that could be addressed if we actually moved forward with something like this issue (Connecting eStack instances).

Other benefits for a parent instance could be aggregate reporting of shop instances, global inventory visibility, eventual omni-channel fulfillment allowing user to ship orders from the closest location to the customer that has afvailable stock. Many more benefits as well.

This could be something pretty complex that we can get budget for post-POS and post-BoM (or before BoM if it's a good thing to build at this stage)

@tim What do you think about some service that would allow a company like ZR or Cbus to connect eStack instances as dependent or shared locations? Goal would be to allow synchronization of new SKU data, images and automatic inventory movements for shipments. Right now, to add shipment stock to the shops I have to: 1) Download the catalog from ZR warehouse instance (parent or main instance) 2) Copy product catalog and supplier data to the Bulk Upload form to bulk create SKUs. 3) Download the Shipment Invoice csv for a zeneroe.estack.com shipment 4) Open it in LibreOffice and copy the SKU column into the Supplier SKU column so I can upload (shop locations all use the same SKUs as the zeneroe.estack.com parent instance). 5) Go to Manage Supplier Invoices in the shop instances and upload the Shipment Invoice csv. 6) Go to QC and move the stock from QC to another location. We do not need QC at the shops, so this step could be skipped. I think I created an issue to make QC optional overall, but that's not a priority. I assume that could be addressed if we actually moved forward with something like this issue (Connecting eStack instances). Other benefits for a parent instance could be aggregate reporting of shop instances, global inventory visibility, eventual omni-channel fulfillment allowing user to ship orders from the closest location to the customer that has afvailable stock. Many more benefits as well. This could be something pretty complex that we can get budget for post-POS and post-BoM (or before BoM if it's a good thing to build at this stage)

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rob/pms3#371