Ship

• Release software → deliver · launch · push live · get out of the door
• Send goods → dispatch · send · deliver · freight
• Approve (imperative) → "ship it" = looks good, go ahead
• Pair fictional people (internet slang) → root for a couple

The word comes from cargo: a ship in the harbour is not shipping anything. The moment the metaphor moves to software, it keeps that condition — it has to leave. This is why native speakers can say a sentence that sounds strange to a learner:

"The code is done, but we haven't shipped yet."

Done and shipped are two different states. Slavic languages tend to mark completion (зробив, готово) rather than departure, so learners reach for finished when the client wants to hear shipped.

The practical test: can a user touch it right now? If no, it isn't shipped — whatever you have finished.

This is also why ship is the strongest word you have in a status update. "The feature is finished" invites the question "so where is it?" — "We shipped it Tuesday" ends the conversation.

• "We shipped on Thursday."
• "We shipped the new dashboard last sprint."
• "I'd rather ship something small this week than something perfect next month."
• "Nothing shipped in December — the whole team was out."
• "Let's ship it and iterate."

One vowel, one final consonant, stressed syllable → double the p: shipped, shipping, shipper. ✗ shiped · ✗ shiping are the two most common written errors here. Same rule as stop → stopped, plan → planned.

• "We ship every two weeks." (a cadence — the release rhythm of the team)
• "We shipped the payment flow behind a feature flag." (technically live, visible to a subset — still counts as shipped)
• "That won't ship this quarter." (a scope decision, not a coding problem)

Note the second one: shipped is about availability, not about announcement. A silent release is still a release.

• "Your order shipped this morning." (the seller's standard phrasing — note the active verb with the parcel as subject)
• "We ship worldwide." (a company policy line)
• "The laptop ships from Germany, so expect a week." (present simple for a scheduled, repeatable process)

This sense is where you'll meet the word as a customer, and it's worth knowing because the passive is often dropped: your order shipped, not your order was shipped, is the normal e-commerce sentence.

• "Ship it. 🚢" (a full code review approval, one word plus an emoji)
• "Two small nits, otherwise ship it." (the standard reviewer sentence — concede first, approve after)
• "LGTM, ship it."

This is an imperative used as a verdict, and one of the few pieces of workplace slang that's safe with almost any tech client. It carries a specific attitude: this is good enough, stop polishing.

• "I ship them so hard."
• "They're my favourite ship."

Worth recognising so you're not confused on social media. Never use it in a professional message, where it will read as a typo at best.

• ❌ "We shipped it on production" → ✅ "We shipped it to production"
• ❌ "We ship in Friday" → ✅ "We ship on Friday"
• ❌ "shipped to the client the invoice" → ✅ "shipped the client the invoice" / "the invoice to the client"

You ship features, products, code, versions, fixes. You do not ship tasks, tickets, or hours.

• ❌ "I shipped the ticket" → ✅ "I closed the ticket" / "I shipped the fix"
• ❌ "We shipped a release" → ✅ "We shipped" / "We cut a release" (shipping a release is doubled — the release is the shipping)

• ❌ "We are shipping it yesterday" → ✅ "We shipped it yesterday"
• ✅ "We're shipping on Friday." (present continuous for a fixed near-future plan — the natural form for a scheduled release)
• ✅ "We ship every two weeks." (present simple for the recurring rhythm)

• ❌ "The feature was shipped by our team yesterday."
• ✅ "We shipped the feature yesterday."

English status reports are agent-first. The passive is correct grammar but wrong register; it sounds evasive, as though nobody wants to own the release.

• "We'll ship on Friday" = Friday, that day. If it lands Wednesday, you were early but you promised Friday.
• "We'll ship by Friday" = Friday at the latest. This is the safer commitment and the one to use in a client email.

Default to by in anything a client might hold you to. On is for a date you actually intend to hit exactly — a coordinated launch, a press embargo, a contractual milestone.

• build / implement → it exists in your editor
• merge → it's in the main branch, nobody outside can see it
• deploy → it's on a server, possibly staging, possibly nobody's using it
• release → the neutral, formal word for making a version available
• ship → the same event, said with energy and ownership
• launch → release plus announcement, marketing, a moment
• roll out → release gradually, in stages or by region

Deploy is a technical act. Ship is a commitment kept. Launch is an event with an audience.

You can deploy ten times a day and ship nothing. You can ship without launching. You cannot launch without shipping.

Реалізувати / реализовать is implement, not realise. "We realised the feature" means you suddenly became aware of it.

And отгрузить in Russian dev slang is a direct calque of ship — the instinct is right, but say it in English as ship, not unload or offload.

• "We ship behind flags, so nothing goes out to everyone at once."
• "The build is green — shipping now."
• "This is ship-blocking, let's fix it before release." (a blocker to shipping, not a broken build)
• "Nice work. One nit on naming, otherwise ship it."
• "We shipped a hotfix within twenty minutes of the report."
• "I'd rather not ship this on a Friday afternoon." (the universal joke that is not really a joke)

• "We shipped the reporting module on Tuesday — it's live on your staging environment."
• "We'll ship by Friday at the latest." (safe commitment)
• "Realistically, we can ship the core flow this sprint and the exports next." (scope split, no apology needed)
• "The API change is shipped; the frontend follows next week."
• "Happy to ship this in two stages if you'd like the search live sooner."

With a startup, agency, or technical founder, ship is warm and confident — it signals you belong.

With a bank, a law firm, or any non-technical stakeholder, prefer release, deliver, or go live. Some clients hear ship as jargon and, worse, some hear it as rushed.

• "My order still hasn't shipped."
• "They ship to Moldova, but the customs fee is brutal."
• "I finally shipped that side project I've been sitting on for a year."
• "She ships fast and fixes later — that's just how she works."
• "Anything that ships from China takes a month."

Notice the third and fourth: the tech sense has escaped into general speech. Shipping a personal project, a newsletter, a video — any creator can use it, and it always carries the same meaning: you stopped hiding it.

🚢 Finished is not shipped. Merged is not shipped. Deployed to staging is not shipped.

It has to leave you and reach someone else.

1. to production — not on production.
2. by Friday. On Friday promises that specific day; by Friday makes Friday the deadline and any earlier day a win.
3. shipped — double the p before -ed and -ing. ✗ shiped · ✗ shiping

1. Your code is merged into the main branch but not deployed anywhere. Has it shipped? No. Nothing outside your team can reach it. Merged is not shipped.

2. Fix this: "The new dashboard was shipped by our team last week." ✅ "We shipped the new dashboard last week." — active voice, agent first. The passive sounds evasive in a status update.

3. A reviewer writes "Two small nits, otherwise ship it." Are you approved to merge? Yes. Ship it is the approval; the nits are optional polish, not conditions. If they were conditions, the reviewer would have requested changes.

4. Your product went live quietly — no announcement, no blog post, no email. Did you ship it? Did you launch it? Shipped, yes. Launched, no. Shipping is availability; launching is availability plus an audience being told about it.

Roughly — all use cases · Ideally / Realistically for the estimate register that pairs with shipping dates · Roll out for the gradual-release sibling.