Eniteo 13.02.29 is a focused follow-up to 13.02.28, building on a few of that release’s capabilities. It adds an optional approval workflow to Warehouse Transfers, giving multi-location operations control over inventory movement between warehouses, and extends the EDI Advance Ship Notice (ASN) shipping experience with a pre-send confirmation step and failure recovery. The release also delivers fixes across customer statements, tax handling, production orders, and EDI receiving.
Approval Workflow added to Warehouse Transfers
Operations that run multiple warehouses regularly move inventory between locations to balance stock and fulfill orders, and many want a checkpoint before that material is committed — a way for the supplying or producing location to review what another warehouse is asking for and decide whether to fulfill it.
With this release, administrators can enable an optional feature that adds an approval workflow for stock transfer requests — transfers not tied to a sales order. A requesting location submits a stock transfer request, an approving location reviews the pending requests and approves or declines each line, and approved lines flow on to a shipping-ready transfer with a complete record of who requested the material, who approved it, and when.
Requesters and approvers work from the same Warehouse Transfers screen, which adapts based on whether the current user has approval rights for the warehouse they are working in. The entire workflow is controlled by a new Enable Transfer Approval setting on the Inventory tab of Application Control; when it is turned off, Warehouse Transfers continues to work exactly as it does today.
A new Transfer tab in Employee Maintenance lets administrators set per-warehouse Can Approve permission for each employee. Any employee can submit a transfer request from any warehouse; only employees with Can Approve for a given warehouse can review and approve requests that originate there. The Warehouse Transfers screen adapts based on whether the current user has Can Approve for the selected From Warehouse.
When a user without Can Approve for the selected From Warehouse opens the screen, it enters Request mode — clearly indicating that approval is required and labeling the document a Request. The lines they add are created in a Pending status, stamped with the requesting user and time, and the requester can see each line’s status as it progresses.
An approver — any user with Can Approve for that From Warehouse — sees the pending stock transfer requests in the grid alongside available sales orders, with Approve and Reject actions on each pending request row.
Approving a line moves it onto the approver’s transfer — with a link back to the original request — and stamps it Approved with the approver and time; declining a line marks it Rejected. In every case the requester’s view updates and the decided line locks, so both sides have a clear record of who requested, who decided, and when.
Approvers can also assign a production process to a transfer line, drawn from the source warehouse’s process list — useful when the producing location fulfills a request by processing material (for example, slitting or leveling) rather than pulling finished stock. Lines that carry a process route into Production Order Entry and flow through Production Order Processing and Post Production before continuing through the standard transfer shipping and receiving steps. The ability to add a process to a transfer line was introduced in the Eniteo 13.02.28 release notes under Production Processing added to Stock Transfer Lines; in this release, when the approval workflow is enabled, only the approving (producing) location can assign it, and one process can still be applied per line.
Send Confirmation and Retry added to Outbound ASN (EDI)
When sending Advance Ship Notices (ASNs) to trading partners through EDI, the outbound export now opens in a confirmation view that lists each ASN with its BOL number in a Pending state. Transmission begins when the shipping clerk selects Send Now, so they can confirm exactly what will be sent before anything leaves Eniteo.
After sending, each row shows its result.
If any transmissions do not complete, a Retry Failed action re-attempts only those rows, leaving the ones that already succeeded untouched. An ASN that has already been sent can be re-sent individually with a per-row Resend, which surfaces a duplicate-send warning so a repeat transmission is always a deliberate choice.
Bug Fixes
- Avalara Integration: Fixed an issue where changing the ship-to address on a Command Center sales order did not update the tax type and rate for an Avalara customer. The tax now matches the selected ship-to — using that address’s own tax setting when it is on file for the customer, or the customer’s default tax setting when it is not.
- Customer Statements: Fixed an issue where prior-period customer statements printed the statement date using the current month rather than the month of the selected ending transaction date. The statement date now matches the selected ending transaction date.
- EDI Receiving: Fixed an issue where, after importing an inbound ASN for a vendor with several open purchase orders, the Receiving window highlighted the first line rather than the purchase order being received. Receiving now highlights the purchase order that is being received.
- Production Order Entry: Fixed an issue where Production Order Entry and Post Production could close unexpectedly when using Add Master on a line that had a large number of finished material rows. Add Master now completes normally even on lines with hundreds of finished material rows.