New Send to Amazon System and its problems
I wanted to start a thread of the specific problems with the new system.
The first thing that needs to happen is to keep the old system until after Christmas. Never roll something out right before peak season.
Secondly, the old system works perfectly.
-
We can create future plans to make sure we do not over send inventory. I have plans weekly. I manually check inventory levels and sales. If we have enough, I push back sending the item for a week or two. The old system is easy to manage what we need to send. We can name a shipment by date to ship in.
-
The old system is easy to use. We do most of our shipments UPS. We can enter the quantity we need to send and we are done. One good feature of the new system is we can create a template. So for example, if 60 of an item fits in a certain box, we can just create that. In most cases, there is substantial space left in a box, so we fit in smaller items to fill gaps. There is no real use for creating templates for us.
-
Making LTLs. The old system is easy. We add what we want and have our warehouse pack it up. The new system wants each box size. This is an enormous amount of work. We know how much cube to put on a pallet.
-
We pre-print our FNSKU labels. We prepack boxes because we are swamped during Christmas season. The old system makes it really easy to make labels. Plus we can add returns, which need new labels created. This works perfectly in the old system.
I am looking for feedback on what works now that does not work in the new system.
New Send to Amazon System and its problems
I wanted to start a thread of the specific problems with the new system.
The first thing that needs to happen is to keep the old system until after Christmas. Never roll something out right before peak season.
Secondly, the old system works perfectly.
-
We can create future plans to make sure we do not over send inventory. I have plans weekly. I manually check inventory levels and sales. If we have enough, I push back sending the item for a week or two. The old system is easy to manage what we need to send. We can name a shipment by date to ship in.
-
The old system is easy to use. We do most of our shipments UPS. We can enter the quantity we need to send and we are done. One good feature of the new system is we can create a template. So for example, if 60 of an item fits in a certain box, we can just create that. In most cases, there is substantial space left in a box, so we fit in smaller items to fill gaps. There is no real use for creating templates for us.
-
Making LTLs. The old system is easy. We add what we want and have our warehouse pack it up. The new system wants each box size. This is an enormous amount of work. We know how much cube to put on a pallet.
-
We pre-print our FNSKU labels. We prepack boxes because we are swamped during Christmas season. The old system makes it really easy to make labels. Plus we can add returns, which need new labels created. This works perfectly in the old system.
I am looking for feedback on what works now that does not work in the new system.
15 replies
Seller_ggTMcPgubvwWj
This is our biggest issue - under the current and significantly more efficient system, shipment splits are created with individual and accessible shipment IDs that can be renamed by the seller, such as FBAXFER-2829884 - 1, before confirming the shipments. These independent IDs allow our system to identify and pull down each shipment list and parse the original upload into however many shipments Amazon requires. Shipment creation, pick/pack/ship, and upload verification are extremely automated and smooth via this workflow.
Under STA, this incredibly important identifier is completely missing in Step 1b. It’s great that we can pack boxes however we want within the same pack group, but since the pack groups do not have individual IDs accessible from the developer side, there is no way to automate the pick route parsing described above. Warehouses can’t pack boxes if they haven’t picked the product, and they can’t pick the product if there aren’t developer-accessible IDs to identify/download/parse the pack lists. This turns the STA workflow into an adversely manual one (manual pick sheets instead of electronic routes; manual box packing/tracking instead of scan-to-box pack lists; etc.).
Our only hope is that Amazon gets to October 15, realizes how much FBA business will drop off if they force a very case-centric shipment module on all sellers, and backtracks to allow both systems to work side-by-side indefinitely.
Seller_EvILRTz0rQ5dk
Copying this over from a user in the previous thread -
Need to be able to name workflows upon creation
Need to be able to load case pack information (dims/weights/qty) in bulk
Need to better generate packlists – the old packing lists were perfect. Literally just copy it.
Need to have 2D barcodes available
NEED to have storage category labeled on SKUs within a workflow. If I exceed limits within a storage category, there’s no way of easily knowing which SKU is the culprit without manually checking each one.
Need to be able to modify quantities after loading with a file upload. Right now you can only modify quantities when you added SKUs to a workflow manually.
These changes are the bare minimum for this system to even work remotely fluidly at scale. The fact that after over two months of “listening to our feedback” we can’t even get custom names on our workflows which literally everyone has been asking for since day 1…it really speaks volumes about this whole thing.
Best Regards
Seller_hqjo3wRnowVz7
The new STA feature has so many problems I dont think they can all be listed, it is one of the worst, and most poorly designed pieces of software I have ever seen. To call it a total pile of garbage would be an understatement
Seller_dn7C3zOSYPPIw
My biggest issue is that when a single workflow gets split into multiple shipments, they force you to pick EITHER Amazon Partnered Carrier OR non-APC for ALL shipments.
APC for full truckloads = ridiculously expensive and honestly, amateurish. I’m fine with Estes or Amazon LTL taking a pallet halfway across the country, but not for FTL shipments.
Seller_bDjLrI5DCEUE5
Am I the only one who shows 0 SKUs (0 units) for all workflows even though they have multiple SKUs and sometimes 1000’s of units?
Seller_UNEafkfdd0cjS
Context: I have only made one workflow with the new system.
Here are couples things I would like to see improve
1.Adding the ability to add more product after I upload a file in would be nice. The only way to do that right now is to make a new workflow as far as I know
2.Deleting products before confirmation is glitchy. There was a item that i couldn’t send because of some internal issue, but i couldn’t delete it off the workflow for some reason, and had to restart the workflow. This is before confirmation too
- Add the ability to add extra lines for packaging info in the upload file option. I know i can add a line in the “select from list”, but i can’t find a way to do that with the uploading template method. and if i try to use select from list after i upload a file, it tells me to restart workflow.
4.When i download packing list of a shipment, the excel it populate has issues: 1. if the product description is too long, it pushes the description into a 2nd cell and pushes all the information down, which adds more work for us when we want to use the information to pull the items. 2. the SKUs arn’t in numerical order. This isn’t a big problem because i can just sort it, but why is it not in numerical order but the carton labels that it generate are in numerical order?
-
Add the ability to change case pack information after confirmation would be really nice, although i don’t see them adding this method.
-
add the ability to delete products after confirmation would be nice too, but i don’t seem them adding this method either in the future. (not having 5,6 made our work a lot harder).
-
when i had to make a 5% or 6 unit change after confirmation, the carton label it generate does not reflect that change, this caused confusion to our warehouse team.
-
Breakdown of cost per shipment: maybe i missed it somewhere but all i can see is the total cost of all shipments in the workflow, Maybe if it’s somewhere but i couldn’t find it. would be nice to have for our accounting team.
if any of those above are things that i just overlooked and already have solution, please let know know. It would help me a lot.
Here’s are some personal complaints:
This whole process is so convoluted for us because we have over 900+ active SKUs. Putting together all the dim and weight information for one workflow is so much work. Trying to mess around with excel to make it easier but it still adds so much more work and so much more mandatory communication with the warehouse.
Seller_Qbd0RsfZFEZBY
Change is the only constant. Progress for progress sake is the zeitgiest.
I dont know that AMZ wants thier FBA inventory replentishment systems used for your internal planning. We use Excel and take inventory once a week unless we have a run on a certain SKU.
We also are primarily UPS.
I like this feature as well but unlike your situation our products come in a standard case pack so the template is very nice.
Part of the new system is the backend reconsiles the item size to the case pack/box/pallet. This keeps sellers honest when sending in inventory. We use a standardized box size to make this easier. 16x12x12 stacks very well and is the cheapest specific box size in the 14-18 inch size range on Uline.
We do not use AMZ systems to make any labels. Its slow and not the easiest to navigate. Nor can you make custom labels like “Sell as Set”.
Zebra label printers and software is easy and intuitive and prints 6 per second. Just remember to use 128-A UPC format for AMZ, and dont go to large. They like 2x4 or below and keep your UPCs between 1 and 4 inches.
Seller_EvILRTz0rQ5dk
Mods, can we please get an update? Any news? It has been a month since the deadline has been pushed, and none of the bugs/issues have been addressed.
New Send to Amazon System and its problems
I wanted to start a thread of the specific problems with the new system.
The first thing that needs to happen is to keep the old system until after Christmas. Never roll something out right before peak season.
Secondly, the old system works perfectly.
-
We can create future plans to make sure we do not over send inventory. I have plans weekly. I manually check inventory levels and sales. If we have enough, I push back sending the item for a week or two. The old system is easy to manage what we need to send. We can name a shipment by date to ship in.
-
The old system is easy to use. We do most of our shipments UPS. We can enter the quantity we need to send and we are done. One good feature of the new system is we can create a template. So for example, if 60 of an item fits in a certain box, we can just create that. In most cases, there is substantial space left in a box, so we fit in smaller items to fill gaps. There is no real use for creating templates for us.
-
Making LTLs. The old system is easy. We add what we want and have our warehouse pack it up. The new system wants each box size. This is an enormous amount of work. We know how much cube to put on a pallet.
-
We pre-print our FNSKU labels. We prepack boxes because we are swamped during Christmas season. The old system makes it really easy to make labels. Plus we can add returns, which need new labels created. This works perfectly in the old system.
I am looking for feedback on what works now that does not work in the new system.
New Send to Amazon System and its problems
I wanted to start a thread of the specific problems with the new system.
The first thing that needs to happen is to keep the old system until after Christmas. Never roll something out right before peak season.
Secondly, the old system works perfectly.
-
We can create future plans to make sure we do not over send inventory. I have plans weekly. I manually check inventory levels and sales. If we have enough, I push back sending the item for a week or two. The old system is easy to manage what we need to send. We can name a shipment by date to ship in.
-
The old system is easy to use. We do most of our shipments UPS. We can enter the quantity we need to send and we are done. One good feature of the new system is we can create a template. So for example, if 60 of an item fits in a certain box, we can just create that. In most cases, there is substantial space left in a box, so we fit in smaller items to fill gaps. There is no real use for creating templates for us.
-
Making LTLs. The old system is easy. We add what we want and have our warehouse pack it up. The new system wants each box size. This is an enormous amount of work. We know how much cube to put on a pallet.
-
We pre-print our FNSKU labels. We prepack boxes because we are swamped during Christmas season. The old system makes it really easy to make labels. Plus we can add returns, which need new labels created. This works perfectly in the old system.
I am looking for feedback on what works now that does not work in the new system.
New Send to Amazon System and its problems
I wanted to start a thread of the specific problems with the new system.
The first thing that needs to happen is to keep the old system until after Christmas. Never roll something out right before peak season.
Secondly, the old system works perfectly.
-
We can create future plans to make sure we do not over send inventory. I have plans weekly. I manually check inventory levels and sales. If we have enough, I push back sending the item for a week or two. The old system is easy to manage what we need to send. We can name a shipment by date to ship in.
-
The old system is easy to use. We do most of our shipments UPS. We can enter the quantity we need to send and we are done. One good feature of the new system is we can create a template. So for example, if 60 of an item fits in a certain box, we can just create that. In most cases, there is substantial space left in a box, so we fit in smaller items to fill gaps. There is no real use for creating templates for us.
-
Making LTLs. The old system is easy. We add what we want and have our warehouse pack it up. The new system wants each box size. This is an enormous amount of work. We know how much cube to put on a pallet.
-
We pre-print our FNSKU labels. We prepack boxes because we are swamped during Christmas season. The old system makes it really easy to make labels. Plus we can add returns, which need new labels created. This works perfectly in the old system.
I am looking for feedback on what works now that does not work in the new system.
15 replies
15 replies
Seller_ggTMcPgubvwWj
This is our biggest issue - under the current and significantly more efficient system, shipment splits are created with individual and accessible shipment IDs that can be renamed by the seller, such as FBAXFER-2829884 - 1, before confirming the shipments. These independent IDs allow our system to identify and pull down each shipment list and parse the original upload into however many shipments Amazon requires. Shipment creation, pick/pack/ship, and upload verification are extremely automated and smooth via this workflow.
Under STA, this incredibly important identifier is completely missing in Step 1b. It’s great that we can pack boxes however we want within the same pack group, but since the pack groups do not have individual IDs accessible from the developer side, there is no way to automate the pick route parsing described above. Warehouses can’t pack boxes if they haven’t picked the product, and they can’t pick the product if there aren’t developer-accessible IDs to identify/download/parse the pack lists. This turns the STA workflow into an adversely manual one (manual pick sheets instead of electronic routes; manual box packing/tracking instead of scan-to-box pack lists; etc.).
Our only hope is that Amazon gets to October 15, realizes how much FBA business will drop off if they force a very case-centric shipment module on all sellers, and backtracks to allow both systems to work side-by-side indefinitely.
Seller_EvILRTz0rQ5dk
Copying this over from a user in the previous thread -
Need to be able to name workflows upon creation
Need to be able to load case pack information (dims/weights/qty) in bulk
Need to better generate packlists – the old packing lists were perfect. Literally just copy it.
Need to have 2D barcodes available
NEED to have storage category labeled on SKUs within a workflow. If I exceed limits within a storage category, there’s no way of easily knowing which SKU is the culprit without manually checking each one.
Need to be able to modify quantities after loading with a file upload. Right now you can only modify quantities when you added SKUs to a workflow manually.
These changes are the bare minimum for this system to even work remotely fluidly at scale. The fact that after over two months of “listening to our feedback” we can’t even get custom names on our workflows which literally everyone has been asking for since day 1…it really speaks volumes about this whole thing.
Best Regards
Seller_hqjo3wRnowVz7
The new STA feature has so many problems I dont think they can all be listed, it is one of the worst, and most poorly designed pieces of software I have ever seen. To call it a total pile of garbage would be an understatement
Seller_dn7C3zOSYPPIw
My biggest issue is that when a single workflow gets split into multiple shipments, they force you to pick EITHER Amazon Partnered Carrier OR non-APC for ALL shipments.
APC for full truckloads = ridiculously expensive and honestly, amateurish. I’m fine with Estes or Amazon LTL taking a pallet halfway across the country, but not for FTL shipments.
Seller_bDjLrI5DCEUE5
Am I the only one who shows 0 SKUs (0 units) for all workflows even though they have multiple SKUs and sometimes 1000’s of units?
Seller_UNEafkfdd0cjS
Context: I have only made one workflow with the new system.
Here are couples things I would like to see improve
1.Adding the ability to add more product after I upload a file in would be nice. The only way to do that right now is to make a new workflow as far as I know
2.Deleting products before confirmation is glitchy. There was a item that i couldn’t send because of some internal issue, but i couldn’t delete it off the workflow for some reason, and had to restart the workflow. This is before confirmation too
- Add the ability to add extra lines for packaging info in the upload file option. I know i can add a line in the “select from list”, but i can’t find a way to do that with the uploading template method. and if i try to use select from list after i upload a file, it tells me to restart workflow.
4.When i download packing list of a shipment, the excel it populate has issues: 1. if the product description is too long, it pushes the description into a 2nd cell and pushes all the information down, which adds more work for us when we want to use the information to pull the items. 2. the SKUs arn’t in numerical order. This isn’t a big problem because i can just sort it, but why is it not in numerical order but the carton labels that it generate are in numerical order?
-
Add the ability to change case pack information after confirmation would be really nice, although i don’t see them adding this method.
-
add the ability to delete products after confirmation would be nice too, but i don’t seem them adding this method either in the future. (not having 5,6 made our work a lot harder).
-
when i had to make a 5% or 6 unit change after confirmation, the carton label it generate does not reflect that change, this caused confusion to our warehouse team.
-
Breakdown of cost per shipment: maybe i missed it somewhere but all i can see is the total cost of all shipments in the workflow, Maybe if it’s somewhere but i couldn’t find it. would be nice to have for our accounting team.
if any of those above are things that i just overlooked and already have solution, please let know know. It would help me a lot.
Here’s are some personal complaints:
This whole process is so convoluted for us because we have over 900+ active SKUs. Putting together all the dim and weight information for one workflow is so much work. Trying to mess around with excel to make it easier but it still adds so much more work and so much more mandatory communication with the warehouse.
Seller_Qbd0RsfZFEZBY
Change is the only constant. Progress for progress sake is the zeitgiest.
I dont know that AMZ wants thier FBA inventory replentishment systems used for your internal planning. We use Excel and take inventory once a week unless we have a run on a certain SKU.
We also are primarily UPS.
I like this feature as well but unlike your situation our products come in a standard case pack so the template is very nice.
Part of the new system is the backend reconsiles the item size to the case pack/box/pallet. This keeps sellers honest when sending in inventory. We use a standardized box size to make this easier. 16x12x12 stacks very well and is the cheapest specific box size in the 14-18 inch size range on Uline.
We do not use AMZ systems to make any labels. Its slow and not the easiest to navigate. Nor can you make custom labels like “Sell as Set”.
Zebra label printers and software is easy and intuitive and prints 6 per second. Just remember to use 128-A UPC format for AMZ, and dont go to large. They like 2x4 or below and keep your UPCs between 1 and 4 inches.
Seller_EvILRTz0rQ5dk
Mods, can we please get an update? Any news? It has been a month since the deadline has been pushed, and none of the bugs/issues have been addressed.
Seller_ggTMcPgubvwWj
This is our biggest issue - under the current and significantly more efficient system, shipment splits are created with individual and accessible shipment IDs that can be renamed by the seller, such as FBAXFER-2829884 - 1, before confirming the shipments. These independent IDs allow our system to identify and pull down each shipment list and parse the original upload into however many shipments Amazon requires. Shipment creation, pick/pack/ship, and upload verification are extremely automated and smooth via this workflow.
Under STA, this incredibly important identifier is completely missing in Step 1b. It’s great that we can pack boxes however we want within the same pack group, but since the pack groups do not have individual IDs accessible from the developer side, there is no way to automate the pick route parsing described above. Warehouses can’t pack boxes if they haven’t picked the product, and they can’t pick the product if there aren’t developer-accessible IDs to identify/download/parse the pack lists. This turns the STA workflow into an adversely manual one (manual pick sheets instead of electronic routes; manual box packing/tracking instead of scan-to-box pack lists; etc.).
Our only hope is that Amazon gets to October 15, realizes how much FBA business will drop off if they force a very case-centric shipment module on all sellers, and backtracks to allow both systems to work side-by-side indefinitely.
Seller_ggTMcPgubvwWj
This is our biggest issue - under the current and significantly more efficient system, shipment splits are created with individual and accessible shipment IDs that can be renamed by the seller, such as FBAXFER-2829884 - 1, before confirming the shipments. These independent IDs allow our system to identify and pull down each shipment list and parse the original upload into however many shipments Amazon requires. Shipment creation, pick/pack/ship, and upload verification are extremely automated and smooth via this workflow.
Under STA, this incredibly important identifier is completely missing in Step 1b. It’s great that we can pack boxes however we want within the same pack group, but since the pack groups do not have individual IDs accessible from the developer side, there is no way to automate the pick route parsing described above. Warehouses can’t pack boxes if they haven’t picked the product, and they can’t pick the product if there aren’t developer-accessible IDs to identify/download/parse the pack lists. This turns the STA workflow into an adversely manual one (manual pick sheets instead of electronic routes; manual box packing/tracking instead of scan-to-box pack lists; etc.).
Our only hope is that Amazon gets to October 15, realizes how much FBA business will drop off if they force a very case-centric shipment module on all sellers, and backtracks to allow both systems to work side-by-side indefinitely.
Seller_EvILRTz0rQ5dk
Copying this over from a user in the previous thread -
Need to be able to name workflows upon creation
Need to be able to load case pack information (dims/weights/qty) in bulk
Need to better generate packlists – the old packing lists were perfect. Literally just copy it.
Need to have 2D barcodes available
NEED to have storage category labeled on SKUs within a workflow. If I exceed limits within a storage category, there’s no way of easily knowing which SKU is the culprit without manually checking each one.
Need to be able to modify quantities after loading with a file upload. Right now you can only modify quantities when you added SKUs to a workflow manually.
These changes are the bare minimum for this system to even work remotely fluidly at scale. The fact that after over two months of “listening to our feedback” we can’t even get custom names on our workflows which literally everyone has been asking for since day 1…it really speaks volumes about this whole thing.
Best Regards
Seller_EvILRTz0rQ5dk
Copying this over from a user in the previous thread -
Need to be able to name workflows upon creation
Need to be able to load case pack information (dims/weights/qty) in bulk
Need to better generate packlists – the old packing lists were perfect. Literally just copy it.
Need to have 2D barcodes available
NEED to have storage category labeled on SKUs within a workflow. If I exceed limits within a storage category, there’s no way of easily knowing which SKU is the culprit without manually checking each one.
Need to be able to modify quantities after loading with a file upload. Right now you can only modify quantities when you added SKUs to a workflow manually.
These changes are the bare minimum for this system to even work remotely fluidly at scale. The fact that after over two months of “listening to our feedback” we can’t even get custom names on our workflows which literally everyone has been asking for since day 1…it really speaks volumes about this whole thing.
Best Regards
Seller_hqjo3wRnowVz7
The new STA feature has so many problems I dont think they can all be listed, it is one of the worst, and most poorly designed pieces of software I have ever seen. To call it a total pile of garbage would be an understatement
Seller_hqjo3wRnowVz7
The new STA feature has so many problems I dont think they can all be listed, it is one of the worst, and most poorly designed pieces of software I have ever seen. To call it a total pile of garbage would be an understatement
Seller_dn7C3zOSYPPIw
My biggest issue is that when a single workflow gets split into multiple shipments, they force you to pick EITHER Amazon Partnered Carrier OR non-APC for ALL shipments.
APC for full truckloads = ridiculously expensive and honestly, amateurish. I’m fine with Estes or Amazon LTL taking a pallet halfway across the country, but not for FTL shipments.
Seller_dn7C3zOSYPPIw
My biggest issue is that when a single workflow gets split into multiple shipments, they force you to pick EITHER Amazon Partnered Carrier OR non-APC for ALL shipments.
APC for full truckloads = ridiculously expensive and honestly, amateurish. I’m fine with Estes or Amazon LTL taking a pallet halfway across the country, but not for FTL shipments.
Seller_bDjLrI5DCEUE5
Am I the only one who shows 0 SKUs (0 units) for all workflows even though they have multiple SKUs and sometimes 1000’s of units?
Seller_bDjLrI5DCEUE5
Am I the only one who shows 0 SKUs (0 units) for all workflows even though they have multiple SKUs and sometimes 1000’s of units?
Seller_UNEafkfdd0cjS
Context: I have only made one workflow with the new system.
Here are couples things I would like to see improve
1.Adding the ability to add more product after I upload a file in would be nice. The only way to do that right now is to make a new workflow as far as I know
2.Deleting products before confirmation is glitchy. There was a item that i couldn’t send because of some internal issue, but i couldn’t delete it off the workflow for some reason, and had to restart the workflow. This is before confirmation too
- Add the ability to add extra lines for packaging info in the upload file option. I know i can add a line in the “select from list”, but i can’t find a way to do that with the uploading template method. and if i try to use select from list after i upload a file, it tells me to restart workflow.
4.When i download packing list of a shipment, the excel it populate has issues: 1. if the product description is too long, it pushes the description into a 2nd cell and pushes all the information down, which adds more work for us when we want to use the information to pull the items. 2. the SKUs arn’t in numerical order. This isn’t a big problem because i can just sort it, but why is it not in numerical order but the carton labels that it generate are in numerical order?
-
Add the ability to change case pack information after confirmation would be really nice, although i don’t see them adding this method.
-
add the ability to delete products after confirmation would be nice too, but i don’t seem them adding this method either in the future. (not having 5,6 made our work a lot harder).
-
when i had to make a 5% or 6 unit change after confirmation, the carton label it generate does not reflect that change, this caused confusion to our warehouse team.
-
Breakdown of cost per shipment: maybe i missed it somewhere but all i can see is the total cost of all shipments in the workflow, Maybe if it’s somewhere but i couldn’t find it. would be nice to have for our accounting team.
if any of those above are things that i just overlooked and already have solution, please let know know. It would help me a lot.
Here’s are some personal complaints:
This whole process is so convoluted for us because we have over 900+ active SKUs. Putting together all the dim and weight information for one workflow is so much work. Trying to mess around with excel to make it easier but it still adds so much more work and so much more mandatory communication with the warehouse.
Seller_UNEafkfdd0cjS
Context: I have only made one workflow with the new system.
Here are couples things I would like to see improve
1.Adding the ability to add more product after I upload a file in would be nice. The only way to do that right now is to make a new workflow as far as I know
2.Deleting products before confirmation is glitchy. There was a item that i couldn’t send because of some internal issue, but i couldn’t delete it off the workflow for some reason, and had to restart the workflow. This is before confirmation too
- Add the ability to add extra lines for packaging info in the upload file option. I know i can add a line in the “select from list”, but i can’t find a way to do that with the uploading template method. and if i try to use select from list after i upload a file, it tells me to restart workflow.
4.When i download packing list of a shipment, the excel it populate has issues: 1. if the product description is too long, it pushes the description into a 2nd cell and pushes all the information down, which adds more work for us when we want to use the information to pull the items. 2. the SKUs arn’t in numerical order. This isn’t a big problem because i can just sort it, but why is it not in numerical order but the carton labels that it generate are in numerical order?
-
Add the ability to change case pack information after confirmation would be really nice, although i don’t see them adding this method.
-
add the ability to delete products after confirmation would be nice too, but i don’t seem them adding this method either in the future. (not having 5,6 made our work a lot harder).
-
when i had to make a 5% or 6 unit change after confirmation, the carton label it generate does not reflect that change, this caused confusion to our warehouse team.
-
Breakdown of cost per shipment: maybe i missed it somewhere but all i can see is the total cost of all shipments in the workflow, Maybe if it’s somewhere but i couldn’t find it. would be nice to have for our accounting team.
if any of those above are things that i just overlooked and already have solution, please let know know. It would help me a lot.
Here’s are some personal complaints:
This whole process is so convoluted for us because we have over 900+ active SKUs. Putting together all the dim and weight information for one workflow is so much work. Trying to mess around with excel to make it easier but it still adds so much more work and so much more mandatory communication with the warehouse.
Seller_Qbd0RsfZFEZBY
Change is the only constant. Progress for progress sake is the zeitgiest.
I dont know that AMZ wants thier FBA inventory replentishment systems used for your internal planning. We use Excel and take inventory once a week unless we have a run on a certain SKU.
We also are primarily UPS.
I like this feature as well but unlike your situation our products come in a standard case pack so the template is very nice.
Part of the new system is the backend reconsiles the item size to the case pack/box/pallet. This keeps sellers honest when sending in inventory. We use a standardized box size to make this easier. 16x12x12 stacks very well and is the cheapest specific box size in the 14-18 inch size range on Uline.
We do not use AMZ systems to make any labels. Its slow and not the easiest to navigate. Nor can you make custom labels like “Sell as Set”.
Zebra label printers and software is easy and intuitive and prints 6 per second. Just remember to use 128-A UPC format for AMZ, and dont go to large. They like 2x4 or below and keep your UPCs between 1 and 4 inches.
Seller_Qbd0RsfZFEZBY
Change is the only constant. Progress for progress sake is the zeitgiest.
I dont know that AMZ wants thier FBA inventory replentishment systems used for your internal planning. We use Excel and take inventory once a week unless we have a run on a certain SKU.
We also are primarily UPS.
I like this feature as well but unlike your situation our products come in a standard case pack so the template is very nice.
Part of the new system is the backend reconsiles the item size to the case pack/box/pallet. This keeps sellers honest when sending in inventory. We use a standardized box size to make this easier. 16x12x12 stacks very well and is the cheapest specific box size in the 14-18 inch size range on Uline.
We do not use AMZ systems to make any labels. Its slow and not the easiest to navigate. Nor can you make custom labels like “Sell as Set”.
Zebra label printers and software is easy and intuitive and prints 6 per second. Just remember to use 128-A UPC format for AMZ, and dont go to large. They like 2x4 or below and keep your UPCs between 1 and 4 inches.
Seller_EvILRTz0rQ5dk
Mods, can we please get an update? Any news? It has been a month since the deadline has been pushed, and none of the bugs/issues have been addressed.
Seller_EvILRTz0rQ5dk
Mods, can we please get an update? Any news? It has been a month since the deadline has been pushed, and none of the bugs/issues have been addressed.
