Seller Forums
user profile
Seller_kSZCywEhJQQ8J

FBA child SKUs showing 0/9 quantity fields, edits to 0 do not persist, and different parents load different row structures

Hi everyone,

I am posting this after receiving an unhelpful reply from Seller Support, because I wanted to investigate the issue myself and see whether anyone else has seen the same behaviour.

I have two different parent listings with FBA child SKUs.

What I found is:

under one parent, the FBA child SKUs show quantity fields as 0

under another parent, the FBA child SKUs show quantity fields as either 9 or 0

These displayed numbers do not match the actual FBA inventory quantities.

I tried changing all the child rows showing 9 to 0.

When I checked again more than two hours later, those rows were still showing 9.

So from my side, the edit to 0 did not persist. I do not know whether the system rejected the change immediately or accepted it and then restored 9, but either way the page did not keep the value I entered.

I then inspected the pages in browser developer tools.

On the parent page where quantity appears, the live DOM contains a numeric input with an ID pattern like:

fulfillment_availability#1.quantity

and kat-aria-label="Quantity".

On the other parent page, the child rows do not expose that same quantity structure in the live DOM. Instead, I can see fields such as colour, external product ID, external product ID type, price, and condition note, but no fulfillment_availability.quantity field in the same inspected row.

So the two parent pages do not seem to be rendering the same child-row structure.

My questions are:

Why would one parent load child rows with a fulfillment_availability.quantity field while another parent does not?

Why would FBA child SKUs show values such as 9 or 0 when those values do not match real FBA stock?

Why does an entered change from 9 to 0 not persist?

Could this be caused by hidden fulfilment logic or a mismatch between FBA and merchant-fulfilled row models?

I am a small seller, not an engineer, so I should not need to inspect HTML just to understand why Amazon is showing quantities that do not match inventory and do not keep my edits.

Has anyone else seen this?

Case ID: 12219284542

47 views
1 reply
Tags:Inventory
00
Reply
user profile
Seller_kSZCywEhJQQ8J

FBA child SKUs showing 0/9 quantity fields, edits to 0 do not persist, and different parents load different row structures

Hi everyone,

I am posting this after receiving an unhelpful reply from Seller Support, because I wanted to investigate the issue myself and see whether anyone else has seen the same behaviour.

I have two different parent listings with FBA child SKUs.

What I found is:

under one parent, the FBA child SKUs show quantity fields as 0

under another parent, the FBA child SKUs show quantity fields as either 9 or 0

These displayed numbers do not match the actual FBA inventory quantities.

I tried changing all the child rows showing 9 to 0.

When I checked again more than two hours later, those rows were still showing 9.

So from my side, the edit to 0 did not persist. I do not know whether the system rejected the change immediately or accepted it and then restored 9, but either way the page did not keep the value I entered.

I then inspected the pages in browser developer tools.

On the parent page where quantity appears, the live DOM contains a numeric input with an ID pattern like:

fulfillment_availability#1.quantity

and kat-aria-label="Quantity".

On the other parent page, the child rows do not expose that same quantity structure in the live DOM. Instead, I can see fields such as colour, external product ID, external product ID type, price, and condition note, but no fulfillment_availability.quantity field in the same inspected row.

So the two parent pages do not seem to be rendering the same child-row structure.

My questions are:

Why would one parent load child rows with a fulfillment_availability.quantity field while another parent does not?

Why would FBA child SKUs show values such as 9 or 0 when those values do not match real FBA stock?

Why does an entered change from 9 to 0 not persist?

Could this be caused by hidden fulfilment logic or a mismatch between FBA and merchant-fulfilled row models?

I am a small seller, not an engineer, so I should not need to inspect HTML just to understand why Amazon is showing quantities that do not match inventory and do not keep my edits.

Has anyone else seen this?

Case ID: 12219284542

Tags:Inventory
00
47 views
1 reply
Reply
1 reply
user profile
Christine_Amazon

Hi @Seller_kSZCywEhJQQ8J

I was checking, and I can see that the team in charge has responded to you recently in the case ID 12219284542.

Let us know if you have any additional questions.

Christine.

00
Follow this discussion to be notified of new activity
user profile
Seller_kSZCywEhJQQ8J

FBA child SKUs showing 0/9 quantity fields, edits to 0 do not persist, and different parents load different row structures

Hi everyone,

I am posting this after receiving an unhelpful reply from Seller Support, because I wanted to investigate the issue myself and see whether anyone else has seen the same behaviour.

I have two different parent listings with FBA child SKUs.

What I found is:

under one parent, the FBA child SKUs show quantity fields as 0

under another parent, the FBA child SKUs show quantity fields as either 9 or 0

These displayed numbers do not match the actual FBA inventory quantities.

I tried changing all the child rows showing 9 to 0.

When I checked again more than two hours later, those rows were still showing 9.

So from my side, the edit to 0 did not persist. I do not know whether the system rejected the change immediately or accepted it and then restored 9, but either way the page did not keep the value I entered.

I then inspected the pages in browser developer tools.

On the parent page where quantity appears, the live DOM contains a numeric input with an ID pattern like:

fulfillment_availability#1.quantity

and kat-aria-label="Quantity".

On the other parent page, the child rows do not expose that same quantity structure in the live DOM. Instead, I can see fields such as colour, external product ID, external product ID type, price, and condition note, but no fulfillment_availability.quantity field in the same inspected row.

So the two parent pages do not seem to be rendering the same child-row structure.

My questions are:

Why would one parent load child rows with a fulfillment_availability.quantity field while another parent does not?

Why would FBA child SKUs show values such as 9 or 0 when those values do not match real FBA stock?

Why does an entered change from 9 to 0 not persist?

Could this be caused by hidden fulfilment logic or a mismatch between FBA and merchant-fulfilled row models?

I am a small seller, not an engineer, so I should not need to inspect HTML just to understand why Amazon is showing quantities that do not match inventory and do not keep my edits.

Has anyone else seen this?

Case ID: 12219284542

47 views
1 reply
Tags:Inventory
00
Reply
user profile
Seller_kSZCywEhJQQ8J

FBA child SKUs showing 0/9 quantity fields, edits to 0 do not persist, and different parents load different row structures

Hi everyone,

I am posting this after receiving an unhelpful reply from Seller Support, because I wanted to investigate the issue myself and see whether anyone else has seen the same behaviour.

I have two different parent listings with FBA child SKUs.

What I found is:

under one parent, the FBA child SKUs show quantity fields as 0

under another parent, the FBA child SKUs show quantity fields as either 9 or 0

These displayed numbers do not match the actual FBA inventory quantities.

I tried changing all the child rows showing 9 to 0.

When I checked again more than two hours later, those rows were still showing 9.

So from my side, the edit to 0 did not persist. I do not know whether the system rejected the change immediately or accepted it and then restored 9, but either way the page did not keep the value I entered.

I then inspected the pages in browser developer tools.

On the parent page where quantity appears, the live DOM contains a numeric input with an ID pattern like:

fulfillment_availability#1.quantity

and kat-aria-label="Quantity".

On the other parent page, the child rows do not expose that same quantity structure in the live DOM. Instead, I can see fields such as colour, external product ID, external product ID type, price, and condition note, but no fulfillment_availability.quantity field in the same inspected row.

So the two parent pages do not seem to be rendering the same child-row structure.

My questions are:

Why would one parent load child rows with a fulfillment_availability.quantity field while another parent does not?

Why would FBA child SKUs show values such as 9 or 0 when those values do not match real FBA stock?

Why does an entered change from 9 to 0 not persist?

Could this be caused by hidden fulfilment logic or a mismatch between FBA and merchant-fulfilled row models?

I am a small seller, not an engineer, so I should not need to inspect HTML just to understand why Amazon is showing quantities that do not match inventory and do not keep my edits.

Has anyone else seen this?

Case ID: 12219284542

Tags:Inventory
00
47 views
1 reply
Reply
user profile

FBA child SKUs showing 0/9 quantity fields, edits to 0 do not persist, and different parents load different row structures

by Seller_kSZCywEhJQQ8J

Hi everyone,

I am posting this after receiving an unhelpful reply from Seller Support, because I wanted to investigate the issue myself and see whether anyone else has seen the same behaviour.

I have two different parent listings with FBA child SKUs.

What I found is:

under one parent, the FBA child SKUs show quantity fields as 0

under another parent, the FBA child SKUs show quantity fields as either 9 or 0

These displayed numbers do not match the actual FBA inventory quantities.

I tried changing all the child rows showing 9 to 0.

When I checked again more than two hours later, those rows were still showing 9.

So from my side, the edit to 0 did not persist. I do not know whether the system rejected the change immediately or accepted it and then restored 9, but either way the page did not keep the value I entered.

I then inspected the pages in browser developer tools.

On the parent page where quantity appears, the live DOM contains a numeric input with an ID pattern like:

fulfillment_availability#1.quantity

and kat-aria-label="Quantity".

On the other parent page, the child rows do not expose that same quantity structure in the live DOM. Instead, I can see fields such as colour, external product ID, external product ID type, price, and condition note, but no fulfillment_availability.quantity field in the same inspected row.

So the two parent pages do not seem to be rendering the same child-row structure.

My questions are:

Why would one parent load child rows with a fulfillment_availability.quantity field while another parent does not?

Why would FBA child SKUs show values such as 9 or 0 when those values do not match real FBA stock?

Why does an entered change from 9 to 0 not persist?

Could this be caused by hidden fulfilment logic or a mismatch between FBA and merchant-fulfilled row models?

I am a small seller, not an engineer, so I should not need to inspect HTML just to understand why Amazon is showing quantities that do not match inventory and do not keep my edits.

Has anyone else seen this?

Case ID: 12219284542

Tags:Inventory
00
47 views
1 reply
Reply
1 reply
1 reply
Quick filters
Sort by
user profile
Christine_Amazon

Hi @Seller_kSZCywEhJQQ8J

I was checking, and I can see that the team in charge has responded to you recently in the case ID 12219284542.

Let us know if you have any additional questions.

Christine.

00
Follow this discussion to be notified of new activity
user profile
Christine_Amazon

Hi @Seller_kSZCywEhJQQ8J

I was checking, and I can see that the team in charge has responded to you recently in the case ID 12219284542.

Let us know if you have any additional questions.

Christine.

00
user profile
Christine_Amazon

Hi @Seller_kSZCywEhJQQ8J

I was checking, and I can see that the team in charge has responded to you recently in the case ID 12219284542.

Let us know if you have any additional questions.

Christine.

00
Reply
Follow this discussion to be notified of new activity