Omakase @ Barracks Row Reservations: How to Book

Omakase @ Barracks Row is a roughly twenty course Edomae sushi counter at 522 8th Street SE, on the Capitol Hill strip that gives it its name. There is no dining room and no table section, only one counter run as a communal seating, with two services a night Tuesday through Saturday at 5:30pm and 8:15pm. Every stool is a prepaid ticket bought in advance on Resy, and that structure is the whole reason the reservation is hard: the house cannot overbook, cannot squeeze in an extra two top and cannot take a walk-in, so the only seats that exist are the ones that go on sale.

How booking Omakase @ Barracks Row actually works

Tickets are sold exclusively through Resy, on the venue’s own listing, and the restaurant is unusually direct about the mechanics. Its FAQ states that reservations go up publicly one day at a time, fourteen days in advance, at 12:01 AM. That is not a weekly batch and not a monthly calendar posting. Just after midnight a single new date becomes bookable, and both of that date’s seatings appear together.

Two things about the ticket matter. You are buying the meal, not holding a table: payment happens at booking and a 22 percent service charge is applied at purchase, with drinks and supplements settled separately on the night. The Resy listing showed $210 per person before tax on 29 August 2026, though a tasting counter reprices with its menu, so confirm the current figure there. And Resy caps the party at four; anything larger is a private buyout of up to fourteen guests, arranged by email rather than through the app.

One caveat on the window. Fourteen days is the published floor, not a ceiling: on 29 August 2026 the calendar actually ran to 19 September, closer to three weeks. Treat the FAQ as the rule and the live calendar as the thing you verify, then count back from whatever date the listing currently ends on. If you have not chased inventory on this platform before, why Resy tables vanish instantly covers the seconds after seats appear, and how far in advance to book puts a two week window in context.

Why the seat is so hard to get

Counter capacity, a prepaid ticket and a midnight opening stack into close to the worst possible conditions for a casual browser. Start with supply: a communal counter seats a couple of dozen people at most across both services, so one night’s entire inventory is smaller than a section of a normal restaurant. Checking on 29 August 2026, thirteen of the sixteen dates on the Resy calendar were sold out and the first bookable night was ten days off, on 8 September. A party of four found nothing at all on either 5 September or 19 September, which is what the four seat cap looks like in practice: four adjacent stools have to come free at once, and they almost never do.

Then the prepaid ticket. At most hard restaurants a fully booked Friday is a soft fact, because a held table costs the holder nothing until the day before. Here the money is already spent, so people who bought a seat turn up, and what does come back is governed by a refund deadline rather than by somebody idly changing their mind. Finally the hour. A 12:01 AM opening rewards one specific person: awake, signed in, card saved, watching a single date they picked days earlier. Check at a reasonable hour the next morning and the date that went up overnight has already been picked over.

The off-peak and back-door angles

If your date is welded to one Saturday, this is a fair fight you will probably lose. Flexibility buys more here than at almost any other DC table. Four levers work, and one is firmly shut:

• Use both seatings, not one. Every service night has a 5:30pm and an 8:15pm sitting, and most people mentally book only one. The meal runs about two hours fifteen minutes, so the late seating ends near 10:30pm, which puts off plenty of weeknight diners. Check both before writing off a date.
• Tuesday and Wednesday. Service runs Tuesday through Saturday, and the front of the week is the least contested part of it. The menu, the chefs and the course count do not change on a Tuesday, only the number of people trying to book it.
• Go smaller. A counter refills from its ends. One or two stools come loose far more often than three or four together, so if you are four and the calendar is bare, booking two pairs into the same seating is often the difference between eating there this month and not.
• The buyout. Groups over four are not a lost cause, just a different door. The restaurant does private buyouts of up to fourteen guests by email, which sidesteps the public Resy calendar entirely.
• No walk-ins, so do not plan around one. This is the back door that is closed. The FAQ is explicit that they cannot accommodate walk-ins, because every seat is pre-booked so the kitchen can order fish against an exact headcount. Worth saying plainly, since walking in at a hard table is a good plan at a lot of rooms and a wasted evening at this one.

When cancelled seats come back

The refund rule is the tell, and it is published. Tickets are non-refundable within 48 hours of the reservation time. Outside that window, changing or cancelling triggers an automatic Resy refund of the original payment, processed back to the card over the following business days.

Read that as a deadline rather than fine print and it tells you when to be looking. Anyone having second thoughts about a two hundred dollar per person dinner has a financial reason to act before their 48 hour mark, which pushes the heaviest return of seats into the stretch just ahead of it, roughly two to three days out from a service. That is a different rhythm from the day before scramble at a restaurant with an ordinary card on file policy, and it is the most useful thing to know about this counter. How cancellation policies shape availability covers why the refund rules set the timing.

A second, thinner window opens right after a date first becomes bookable, when people who grabbed a seat at 12:01 AM spend the next few days rearranging around it. Either way the returned ticket behaves like any other Resy seat: it reappears with no warning, at no predictable hour, and it is gone inside a minute if anyone else is on that page.

Automating the watch

So two moments decide whether you eat here, and both are inconvenient: 12:01 AM fourteen days out, and some unannounced minute two or three days before a service when a prepaid ticket comes back. That is the gap SeatSwiper is built for. You tell it the seating, date range and party size you want at Omakase @ Barracks Row, and it watches that Resy listing around the clock, then books the moment a seat appears, whether that is a new date opening overnight or someone releasing a ticket before the 48 hour cutoff. It books on your own Resy account, in your name, a normal reservation you turn up and use, with nothing resold or transferred. Pricing is plain: your first booking is free, then a flat $5 only when it actually gets you the seat, no subscription, and starting a cancellation watch costs $1 to begin. The limits belong here too. It covers Resy, SevenRooms and OpenTable only, it needs your reservation account connected to book as you, and it can lose a race for a single stool. Better than a midnight alarm, never a guarantee. For the rest of the city, start with the hardest restaurants to book in Washington DC, or line up the same plan for Albi.