I have had the FW13 and FW16 be shipped to me. Its a very smooth process. Expect 2-3 Business days at most.
2 Likes
Then It will be fingers crossed for receiving it this week. Next week I 'm not at home. 
2 Likes
I’ve been checking my spam folder more frequently than I care to admit - nothing there. I didn’t have this problem during my last pre-order. I suspect there must be some delays, but it would be nice to hear that from Framework.
Another report here of a Sage failed payment and then everything successful after manual payment. So I’m hoping to receive it (for my wife) later this week!
1 Like
What time?
Wife received the failed payment e-mail earlier today. We did the manual payment somewhere in the last hour and she received the everything good e-mail shortly after that.
It’s lunch time in San Francisco, so maybe tomorrow 
1 Like
Everyone, it’s the payment time for Batch 1 color versions. It’s good to prepare for your email “Action Required: We are unable to process your order.” Your login account on your banking website may be blocked. You may need to call the bank’s customer support to unlock the login account, then pay manually. Good luck!
5 Likes
Batch 1 colors are starting to ship: FW12 Color Batch 1 Guild - #55 by King_Horse
3 Likes
I finally received my Batch 1 Preparation email last night. Based on the timing, it seems like some of us may have been pushed to Batch 2 for some reason.
1 Like
I’ll guess that it is because of batch 0. Let’s say that there are 250 of your config in batch 1. There are coming 25 in batch 0 with your config, then the last 25 will be silent be in batch 2. Just say that they can produce 250 of any config at once.
If you’re at the end of the line of batch 1 then you have bad luck.
Let’s say that this is my guess dor the reason.
Nobody gets pushed to a different batch. Not technically. But there can be situations where orders from multiple batches will be shipping simultaneously, or even cases where some orders from a later batch will ship before an earlier one.
Basically, the way Framework has explained it in the past is that your order will ship once all parts are available, based on a certain hierarchy (batch number, order date, etc.). If there are two identical orders and everything is ready for both, the one in the earlier batch will ship first. But if someone in batch one’s order can’t ship because it is waiting on a part, but an order from a later batch is not waiting on that part, the order from the later batch may end up shipping first. You didn’t get bumped to a different batch, it’s just that all the parts for your particular configuration aren’t available yet.
For example, imagine batch one orders are shipping, but Framework runs out of chargers. All the other parts are still rolling off the assembly lines and being assembled into machines. All orders from batch one that can be shipped have been. So they may start shipping orders from batch two that don’t contain chargers. Once chargers arrive they will ship the batch one orders that contain chargers before they ship the batch two orders that contain chargers. Depending on how quickly they can fulfill orders, it may work out that all of the waiting orders ship virtually at the same time, even if the earlier batch orders were technically processed first.
That’s just a hypothetical scenario, but several situations like that happened with the FW 16 launch, since there were so many modules and configuration options, and some of the modules ended up having supply issues.
3 Likes
Yeah, same here 
3 Likes
5 Likes