Skip to content
RepWatchForumSign in

InTime sent a 116610 instead of my 114060

Viewing 3 posts - 1 through 3 (of 3 total)
SubAlParticipant

I already have two Submariners and a franken, so this is not confusion about a date window. My InTime (Ryan) invoice says 114060, my approval photographs show a 114060 and the parcel delivered on 12 August contained a 116610. I paid by bank transfer on 20 July, approximately EUR 430 to 470 before postage. Pictures arrived on the 28th and dispatch was confirmed on the 31st. Up to opening the package it was an entirely ordinary transaction.

I photographed the sealed wrapping, the watch as unpacked and the label. I sent those with the invoice on delivery day. Ryan replied asking whether I would keep it at a small discount. I said no, because a date model duplicates something I own and was not what I ordered. Since then I have asked for return arrangements and confirmation that the agreed no-date reference is available. Neither question has been answered. The protective wrapping remains on and I have not sized the bracelet. I am not going to start wearing a watch while somebody decides whether my refusal counts. Mistakes happen; I would have accepted a straightforward correction. At the moment I have the wrong reference and an offer I declined, with no agreed route to put it right.

DialMacroParticipant

Your unpacking photographs should make this unusually clear. Keep a picture of any number on the packaging too, in case two parcels were mixed. I would not send it back to an address copied from an old thread. Get the return instructions attached to this particular order in writing first.

Hollis16610Participant

A discount is a reasonable option to offer once, but you have answered it. My 16610 and 214270 serve different purposes and I would be equally irritated by somebody treating references as interchangeable. Your next useful update will be return instructions or a refund decision. Everything else is circling the issue.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.