如何在 NetSuite 中处理季节性项目
我的组织销售户外设备（帐篷、睡袋等），但在如何在 NetSuite 中处理季节性物品方面遇到了障碍。我们正在为我们的产品团队建立 Centric 作为 PLM 系统，该系统具有从季节开始的产品层次结构（例如 - 从 2022 年开始，选择您的产品类别，然后选择您的产品）。在 NetSuite 中，我们的所有产品当前都设置为非矩阵库存项目，并且我们在字段中附加了“下一季”或“下一季”，以尝试获取项目记录上的所有相关数据。随着我们业务的不断增长，我们遇到了许多问题，并正在努力重新定义我们的项目结构。
棘手的地方 - 我们的销售部门希望每年“相同”的产品共享一个 SKU，以便我们的零售商可以将它们作为相同的库存进行跟踪。然而，从制造或成本计算的角度来看，这些产品每年都不相同（我们可能会转移工厂，或者材料部件价格发生变化，从而改变我们的到岸成本）。根据我的研究，没有什么好的办法可以解决这个问题。我们研究了矩阵项作为可能的解决方案，但它们不太符合需要。
有没有人遇到过类似问题的合理解决方案？我们需要一种方法，要么在一个商品记录上拥有季节性（本质上是时间序列）商品数据，要么拥有共享 SKU 的多个商品记录（每个季节一个），并且可以将其汇总到报告和库存计算中，就好像它们是一件物品。
这里的任何帮助或想法将不胜感激！干杯!
My organization sells outdoor equipment (tents, sleeping bags, etc.) and is hitting a roadblock with how to handle seasonal items in NetSuite. We are in the process of standing up Centric as a PLM system for our Product team, which has a product hierarchy starting with the season (for example - you start with 2022, select your product category, then select your product). In NetSuite, all of our products are currently set up as non-matrix inventory items, and we have fields appended with "Next Season" or "Season After Next" to attempt to have all the relevant data on the item record. We are running into a multitude of issues as our business continues to grow, and are working to redefine our item structure.
The tricky bits - our Sales department would like to have products that are "the same" year to year share a SKU so that our retailers can track them as the same inventory. However, these products are not the same year to year from a manufacturing or costing standpoint (we may shift factories, or have material components pricing change which changes our landed cost). From my research, there is no good way around this. We investigated matrix items as a possible solution, but they don't quite fit the need.
Has anyone come across a reasonable solution for something like this? We need a way to either have seasonal (essentially time-series) item data on one item record, or to have multiple item records (one for each season) that share a SKU and can be rolled into reports and inventory calculations as if they were one item.
Any help or ideas here would be greatly appreciated! Cheers!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
一种可行的方法是使用装配项目。
可以实现此目的的事情：
所以你用 sku X 定义一个程序集
它有一个来自制造商 B 的 sku A 即使最初您可能会给它一个 Spring2022
sku A 的修订版，但它可能是库存商品，但您可能永远没有库存。
这里的下一点是模糊的，因为这取决于您的 PO 管理流程以及您拥有的自动化功能，但您可以：
下个赛季 sku X 将进行新修订，Summer2022，其中 sku A 已退役，并添加了新组件 sku B。您仍然可以履行 2022 年春季修订版，直到您退出，然后开始履行 2022 年夏季修订版。
您的成本从您的组件中累积；您的 SKU 保持稳定。您可以轻松清理旧库存。
为了跟踪每个版本的数量，您可能还需要将它们设置为批号组件。您可以将修订与批号联系起来，自动化可以帮助最大限度地减少协调所需的点击次数。
一项建议是在沙盒帐户中执行您所做的任何操作。这些更改可能有很多细节，您可能会发现自己多次将其撕碎，直到您按照自己想要的方式跟踪成本。
An approach that could work is to use Assembly Items.
The things that can make this work:
So you define an assembly with sku X
It has a single sku A from manufacturer B Even initially you might give it a revision of Spring2022
sku A would be a inventory item but you might never have any in stock.
The next bit here is vague because it depends on your PO management process and what automations you have there but you either:
next season sku X gets a new revision, Summer2022, where sku A is retired and new component sku B is added. You can still fulfill rev Spring 2022 until you are out and then start fufilling rev Summer 2022.
Your costs roll up from you components; your skus stay stable. You have an easy path to clearing old inventory.
In order to track the quantities you have of each revision you would probably need to also set these up as lot numbered assemblies. You could tie the revision to a lot number and automations could help minimize the number of clicks needed to coordinate.
One recommendation is to do whatever you do in a sandbox account. There can be a lot of details to these changes and you might find your self tearing this all apart a couple of times until you are tracking costs the way you want to.
另一种可行的方法是将您的商品设置为从多个供应商处采购。然后，供应商的采购详细信息将作为项目的子列表提供，您可以使用该项目的每个供应商名称为每个项目放置采购订单。您的主要 SKU 仍然保持稳定，您可以使用类似于组装理念的批号来跟踪每个供应商的库存水平。
这是一种更简单的方法，但通过装配修订，您可以使用修订下拉列表来自动设置批次号。如果这变得很重要，那么跳过打开“库存详细信息”对话框将需要更多的自动化工作。
要打开此功能：
Another approach that could work would be to set your items up to be sourced from multiple vendors. The vendor's purchasing details are then available as sublists on the item and you can place POs for each using each vendor's name for the item. Your main sku still stays stable and you could track per vendor stock levels using lot numbers similar to the assembly idea.
This is a simpler approach but with assembly revisions you have the revision drop-down that could be used to automatically set the batch number. Skipping having to open the Inventory detail dialog would be more work to automate if that becomes important.
To turn this on: