Skip to content

Release Notes

Release notes document the evolution of Putaway WMS and provide visibility into changes that are relevant for users and integrators. Each version includes a summary of new functionality, behavior changes, and fixes that may affect operational workflows.

The purpose of this section is to:

  • provide transparency into product changes;
  • help evaluate impact before use;
  • support adoption of new functionality;
  • ensure traceability of changes between versions.

What Release Notes Include

Section titled “What Release Notes Include”

Each version is structured into standard categories:

  • Added - new functionality introduced in the platform.
  • Changed - behavior changes, optimizations, or adjustments to existing functionality.
  • Fixed - fixes for issues identified in previous versions.

Optionally, depending on the complexity of the update:

  • Improved - performance or UX optimizations without major functional impact.
  • Removed - functionality or behavior that has been retired.
  • Breaking changes - changes that may require user action, such as API changes, business logic changes, or operational workflow updates.

Update Frequency

Section titled “Update Frequency”

Release notes are published with each stable application version. Depending on the scope of the changes, updates may include:

  • incremental improvements;
  • functionality extensions;
  • major product changes.

Impact and Compatibility

Section titled “Impact and Compatibility”

Changes described in release notes may affect:

  • operational workflows such as receiving, putaway, picking, packing, dispatching, inventory, stock adjustments, and transfers between locations;
  • order flows, invoicing, AWB, label printing, operational documents, and returns processing;
  • external integrations, including APIs, webhooks, marketplaces, couriers, ERP, invoicing systems, and automated synchronizations;
  • data structure, permissions, plan limits, or how certain features are used.

For versions that introduce significant changes, users should review the full release notes before use.

User Recommendations

Section titled “User Recommendations”
  • Review release notes before using new functionality.
  • Monitor the Breaking changes section for any required adjustments.
  • Test critical workflows after each relevant update.
  • Consult the related documentation for additional details.