Skip to content

Add updated_at field + database trigger into inventory source item table #3444

@tschirmer

Description

@tschirmer

Description (*)

update_at field into the stock inventory table

select * from inventory_source_item limit 10;
+----------------+-------------+------------+----------+--------+
| source_item_id | source_code | sku        | quantity | status |
+----------------+-------------+------------+----------+--------+
|              1 | default     | POS-104002 |   4.0000 |      1 |
|              2 | default     | POS-104003 |   2.0000 |      1 |
|              3 | default     | POS-124005 |   8.0000 |      1 |
|              4 | default     | POS-SFR-6612 |   0.0000 |      1 |
|              5 | default     | POS-104004 |   2.0000 |      1 |
|              6 | default     | POS-104006 |   1.0000 |      1 |
|              7 | default     | POS-104007 |   2.0000 |      1 |
|              8 | default     | POS-104008 |   4.0000 |      1 |
|              9 | default     | POS-104009 |   4.0000 |      1 |
|             10 | default     | POS-104011 |   3.0000 |      1 |
+----------------+-------------+------------+----------+--------+

Expected behavior (*)

Expected behaviour is to add it to the database, and let the database manage the updated_at field on save

Benefits

Currently there is no way of knowing when stock was updated. We're running a sync, and the product update_at isn't changed on stock changes, and the inventory table also is not changed.

This prevents a partial sync to other systems. e.g.

select * from inventory_source_item where updated_at > last_sync_time;

Additional information

Should be available via the api in some fashion, ideally in the export_salable_qty rest api endpoint to allow bulk lookups.

Metadata

Metadata

Assignees

Labels

Feature RequestRequest a new feature to be added by MSI ContributorsIssue: ready for confirmationTriage: Dev.ExperienceIssue related to Developer Experience and needs help with Triage to Confirm or Reject it

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions