For teams that run on Erply
Erply stock transfer between stores by sales
Erply keeps stock per location and can move it with an inventory transfer or a transfer request. Deciding what to move means comparing stock and sales across the stores, and that is spreadsheet work. A partner sells rebalancing between locations for Erply stores.
How it goes today
- Export stock per product for each store.
- Put the sales of the last weeks per store next to it.
- Look for products that stand still in one place and sell in another.
- Agree with the store managers what goes where.
- Create the inventory transfers in the back office one by one.
How it can go
Move slow stock to the store where it sells.
Each week you get a list of products that have not sold in one store for weeks and are running low in another, with a suggested quantity to move and from where. On your yes each line becomes a transfer request in Erply, and the store turns it into a transfer when the goods leave.
Say this in ChatGPT, Claude or Copilot
Your chat gets connected to Hypamoon first, with this request filled in. You paste your Erply key in the portal, never in the chat.
With Hypamoon, each week, compare stock and sales of the last four weeks across our stores in Erply. List products that stand still in one store and run low in another, with a suggested quantity to move. When I approve, create transfer requests in Erply between those stores; the stores make the actual transfer.
You create a separate Erply user for the connection yourself, in a user group that keeps access to the API, and give us your customer code with its user name and password. It stays yours.
More for teams on Erply
- Our reorder points are a year old, so one store runs out while the other sits on stock.
- Every delivery means typing the supplier invoice into Erply, line by line.
- Each morning I log in and run the same sales report, store by store.
- Customers ask when their order ships and I have to look it up order by order.
- Everything for Erply