Seller Forums

Results for "고페이알바 탤례상담 peckpark 페크박컨설팅 호텔주방보조알바 과천시고페이알바일자리 50대아르바이트 철근일당"

(89 results)
user profile
Seller_coYkgVClAKm0i
∙
user profile
Seller_WNiOwmSsRKXsv
∙replied
user profile
Seller_nNAxPfinlhvHE
∙replied
user profile
Seller_nNAxPfinlhvHE
∙replied
user profile
Seller_nNAxPfinlhvHE
∙replied
user profile
Seller_2oAtlj7UwEmtU
∙
user profile
Seller_7PacxW89ekGQ7
∙replied
user profile
Seller_xMYHHmyj8gv9F
∙
user profile
Seller_fIvtkcmv58YR5
∙
user profile
Seller_fcnANlwB930WM
∙replied
Sort by
RecommendedLatest activityRecently createdMost viewedMost voted
Filters
Date/timeAll TimePast dayPast weekPast monthPast 3 monthsPast yearDate range
Quick filters
Discussions
Categories
Tags
Tags will populate based on category selection

Results for "고페이알바 탤례상담 peckpark 페크박컨설팅 호텔주방보조알바 과천시고페이알바일자리 50대아르바이트 철근일당"

(89 results)
user profile
Seller_coYkgVClAKm0i
∙
user profile

Hello,

@Seller_lmwzklfLOK2Ob, I’m disappointed with the outcome of this reimbursements and would appreciate your assistance to this.

The records show multiple inventory disposition changes, and all affected units were reimbursed at only 50% of the approved sourcing cost.

These units were sent to Amazon in new and sellable condition and were not damaged or unsellable before being sent. We also used an Amazon Partnered Carrier for the shipment. The units were subsequently damaged during the Amazon distribution/fulfilment process.

It was mentioned that the 50% reimbursement applies when a unit was already in an unsellable condition prior to the warehouse damage event. However, that does not appear to apply in this case, as the units were sellable before being sent to Amazon and the damage occurred within Amazon’s fulfilment network.

Reimbursement IDs: 9074539152, 9075038812, 9074538262, 9073821812, 9073821162

ASIN: B00FL0P27A

1 vote
0 votes
8 views
0 replies
Latest activity
user profile
Seller_WNiOwmSsRKXsv
∙replied
user profile
Amazon Accounting and Tax discussions
by Seller_WNiOwmSsRKXsv

Hi!

I work for a VAT registered UK business and have been tasked with helping our software developer and bookkeeper obtain and map the data from our Seller account. We use Sage 50.

I've pulled this list of amount-description types from all of our statements to date but I'm struggling to get a definitive answer on which are inclusive or exclusive of VAT. Could you please advise on this?

  • Base fee
  • Commission
  • Digital Services Fee
  • DigitalServicesFee
  • FBAInboundTransportationFee
  • FBAInboundTransportationProgramFee
  • FBAPerUnitFulfillmentFee
  • Micro Deposit
  • RefundCommission
  • ShippingChargeback
  • Subscription Fee
  • Successful charge
  • Tax on fee
  • REVERSAL_REIMBURSEMENT
  • COMPENSATED_CLAWBACK
  • WAREHOUSE_LOST

Any advice would be really welcome.

0 votes
0 votes
0 views
5 replies
Latest activity
user profile
Seller_nNAxPfinlhvHE
∙replied
user profile

I have managed to get a useful message from Amazon with evidence that it is parcelforces issue. I have then contacted our parcelforce account manager who has finally admitted the issue is on their side. I will have to omit customer details but here is the response from Amazon, hopefully you can use some of the info to help you. I had to show Amazon a screenshot of the delivery report from the customer, alongside a picture of the tracking that shown the item was still in transit.

I can confirm that I have reviewed the carrier tracking event data received by Amazon's system for all three affected orders, and the data shows a clear pattern that contradicts Parcelforce's position.

For order 111111 with tracking 111111111, Amazon's system received a delivered event from Parcelforce at 16:06on25 September 2026, followed by an out for delivery event at 17:13 on the same date. The delivered status was recorded67 minutes before the parcel was even dispatched for delivery.

For order 111111111 with tracking 11111111111, Amazon's system received a delivered event from Parcelforce at 16:08 on 25 September 2026, followed by an out for delivery event at 17:11 on the same date. Again, the delivered status was recorded 63 minutes before the parcel went out for delivery.

For order 1111111111 with tracking 111111111111, Amazon's system received a delivered event from Parcelforce at 15:50 on 5 October 2026, followed by an out for delivery event at 17:08 on the same date. The delivered status was recorded 78 minutes before the parcel went out for delivery.

In all three cases the delivered event originated from Manchester PFW Depot and was received by Amazon's system before the out for delivery event. This is the data Amazon's system acted on when updating the buyer-facing order status.

Please share these scans with your Parcelforce account manager, as this data confirms that the premature delivered scans were sent from their depot before the parcels had left for delivery.

0 votes
0 votes
0 views
11 replies
Latest activity
user profile
Seller_nNAxPfinlhvHE
∙replied
user profile

I have managed to get a useful message from Amazon with evidence that it is parcelforces issue. I have then contacted our parcelforce account manager who has finally admitted the issue is on their side. I will have to omit customer details but here is the response from Amazon, hopefully you can use some of the info to help you. I had to show Amazon a screenshot of the delivery report from the customer, alongside a picture of the tracking that shown the item was still in transit.

I can confirm that I have reviewed the carrier tracking event data received by Amazon's system for all three affected orders, and the data shows a clear pattern that contradicts Parcelforce's position.

For order 111111 with tracking 111111111, Amazon's system received a delivered event from Parcelforce at 16:06on25 September 2026, followed by an out for delivery event at 17:13 on the same date. The delivered status was recorded67 minutes before the parcel was even dispatched for delivery.

For order 111111111 with tracking 11111111111, Amazon's system received a delivered event from Parcelforce at 16:08 on 25 September 2026, followed by an out for delivery event at 17:11 on the same date. Again, the delivered status was recorded 63 minutes before the parcel went out for delivery.

For order 1111111111 with tracking 111111111111, Amazon's system received a delivered event from Parcelforce at 15:50 on 5 October 2026, followed by an out for delivery event at 17:08 on the same date. The delivered status was recorded 78 minutes before the parcel went out for delivery.

In all three cases the delivered event originated from Manchester PFW Depot and was received by Amazon's system before the out for delivery event. This is the data Amazon's system acted on when updating the buyer-facing order status.

Please share these scans with your Parcelforce account manager, as this data confirms that the premature delivered scans were sent from their depot before the parcels had left for delivery.

0 votes
0 votes
0 views
6 replies
Latest activity
user profile
Seller_nNAxPfinlhvHE
∙replied
user profile

I have managed to get a useful message from Amazon with evidence that it is parcelforces issue. I have then contacted our parcelforce account manager who has finally admitted the issue is on their side. I will have to omit customer details but here is the response from Amazon, hopefully you can use some of the info to help you. I had to show Amazon a screenshot of the delivery report from the customer, alongside a picture of the tracking that shown the item was still in transit.

I can confirm that I have reviewed the carrier tracking event data received by Amazon's system for all three affected orders, and the data shows a clear pattern that contradicts Parcelforce's position.

For order 111111 with tracking 111111111, Amazon's system received a delivered event from Parcelforce at 16:06on25 September 2026, followed by an out for delivery event at 17:13 on the same date. The delivered status was recorded67 minutes before the parcel was even dispatched for delivery.

For order 111111111 with tracking 11111111111, Amazon's system received a delivered event from Parcelforce at 16:08 on 25 September 2026, followed by an out for delivery event at 17:11 on the same date. Again, the delivered status was recorded 63 minutes before the parcel went out for delivery.

For order 1111111111 with tracking 111111111111, Amazon's system received a delivered event from Parcelforce at 15:50 on 5 October 2026, followed by an out for delivery event at 17:08 on the same date. The delivered status was recorded 78 minutes before the parcel went out for delivery.

In all three cases the delivered event originated from Manchester PFW Depot and was received by Amazon's system before the out for delivery event. This is the data Amazon's system acted on when updating the buyer-facing order status.

Please share these scans with your Parcelforce account manager, as this data confirms that the premature delivered scans were sent from their depot before the parcels had left for delivery.

0 votes
0 votes
0 views
6 replies
Latest activity
user profile
Seller_2oAtlj7UwEmtU
∙
user profile
Delivery dates and padding
by Seller_2oAtlj7UwEmtU
Amazon replied

All my items are shipped tracked 24 and will arrive within 1-2 days. Yet my delivery dates are showing 7-8 days for delivery. It’s absolutely ridiculous I have went from selling £4000 a day to selling £700. Can’t sustain my business this way, if it was true fair enough but it’s so incredibly inaccurate. I send same day until 2pm so I would say 50% AT LEAST arrives next day and 50% 2 days MAX.

1 vote
0 votes
64 views
6 replies
Latest activity
user profile
Seller_7PacxW89ekGQ7
∙replied
user profile
Incorrect reimbursement
by Seller_7PacxW89ekGQ7

I have checked that information, they are now using the correct sourcing cost but only reimbursing 50% of it despite accepting that I was given incorrect information regarding the disposal throughout the process and was not able to have the units returned to me. I would appreciate if you could look into this for me as I am seeking 100% of the sourcing cost as reimbursement

0 votes
0 votes
0 views
3 replies
Latest activity
user profile
Seller_xMYHHmyj8gv9F
∙
user profile

My Amazon UK selling account was deactivated on 29 September 2026 due to product authenticity concerns for ASIN B09TLFY4GP.

I have submitted original supplier invoices covering the 280 units requested by Amazon, together with payment, shipping and authorization/authenticity evidence.

However, the latest response states:“Supplier name: SKIN1004”This appears to be a misunderstanding of the submitted documentation.

SKIN1004 is the brand, not our direct supplier.

Our direct suppliers shown on the invoices are:

Craver Corporation / UMMA – 130 unitsAsianBeautyWholesale (Hong Kong) Limited – 150 unitsSKIN1004’s official website also lists UMMA as an Authorized Seller.

The 280 units are fully reconciled to our original purchase invoices:

ABW – 50 units – 11 Sep 2025 ABW – 100 units – 15 Oct 2025 Craver/UMMA – 100 units – 17 Nov 2025

Craver/UMMA – 30 units – 27 Apr 2026

Total: 280 unitsThe 50 units purchased on 11 September 2025 were opening inventory before sales commenced in October 2025, which is why that purchase invoice predates the corresponding sales period.

I would greatly appreciate it if an Amazon moderator could review the case and, if appropriate, escalate it for a manual review of the supplier documentation.

0 votes
0 votes
9 views
1 reply
Latest activity
user profile
Seller_fIvtkcmv58YR5
∙
user profile

Hello Amazon Moderators,

I urgently need assistance with an ongoing suspected inventory-hold / abusive ordering incident on our Amazon UK account.

Seller Support Case ID: 13297740942

This activity has been continuing for more than 48 hours and is still happening right now.

Several of the affected bundle listings normally receive only around 2–3 orders per day. However, we suddenly started receiving abnormal orders approximately every 30 minutes.

We have currently identified 50 separate suspicious Order IDs. What makes the pattern particularly concerning is that every one of these orders contains exactly 5 products.

The pattern is:

• 39+ separate Order IDs identified so far

• Exactly 5 products in each order

• New orders appearing approximately every 30 minutes

• Pattern continuing for 48+ hours

• Orders remaining Pending / Unshipped

• FBA inventory being reserved

• Normal sales velocity is only around 2–3 orders per day on the affected listings

• The activity is still continuing as I write this post

Because these orders remain Pending/Unshipped, our available FBA inventory is being progressively reserved, creating a serious risk that the affected listings will be forced out of stock and become unavailable to genuine customers.

We have already opened Seller Support case 13297740942 and provided the suspicious Order IDs and details, but the activity has not stopped.

We are not making any assumptions about who is responsible. We are asking Amazon to investigate whether these orders are connected and whether this represents deliberate inventory-holding abuse.

Could an Amazon moderator please review Case ID 13297740942 and escalate this to the appropriate Buyer Abuse / Marketplace Abuse investigation team?

This is an active incident rather than a historical issue. New suspicious orders are continuing to appear while we wait for assistance.

Any urgent help from the moderator team would be greatly appreciated.

Thank you.

@Seller_WIFV02H2XUFgS

3 votes
0 votes
137 views
5 replies
Latest activity
user profile
Seller_fcnANlwB930WM
∙replied
user profile

They have removed over 50 for me. They decided Penguin and Middleton Press were brands.

0 votes
0 votes
0 views
68 replies
Latest activity