WhatsApp or Instagram DMs for cake orders: where the pictures live

A cake order is unusual among small-business transactions: it is a visual specification, agreed weeks ahead, with a date that cannot move and money paid in two parts. Instagram is excellent at the first of those and has nothing to offer the rest.

That is the actual comparison. Not which app is better, but which parts of an order each can carry — and specifically what happens to the reference images, which are the part of the specification most likely to be lost.

What we'll cover

• A cake order is four things
• Instagram carries the pictures
• What it cannot carry
• Building it with CodeWords
• Getting the images onto the order
• Moving the conversation
• The saved-post problem
• Running both without losing anybody
• Posting the finished cake
• Making it survive
• Limits worth knowing about
• What to do first
• Frequently asked questions

A cake order is four things

A visual specification, which is images plus a conversation about them.

A date, which is fixed and is the thing everything else hangs on.

A price and a payment, in two parts, weeks apart.

A collection or a delivery, with logistics of its own.

Instagram handles the first and none of the other three.

That is the whole comparison, and it explains why bakers who take orders in DMs describe the same three problems.

Instagram carries the pictures

It is where customers find you, and for a visual trade that is the shop window.

Your portfolio is the product, in a way it is not for most businesses.

Customers arrive having seen your work, which is a better starting point than any description.

They send references from there — a saved post, something they liked, a style.

Tagging and sharing brings new customers in a way messaging cannot.

None of this should move, which is the point most often missed in a comparison like this.

What it cannot carry

No date handling. A DM cannot tell you that Saturday is full.

No payment, so deposits happen elsewhere anyway.

No order state, so a confirmed order and an unanswered enquiry look identical.

No record you can work from on the morning you are baking.

Requests are filtered, and a new customer's first message can sit unseen for days.

It is one person's phone, which is a problem the first time you are ill.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: what happens on an enquiry, where the order is recorded, and how images are attached.
3. Authorize the connections to wherever orders live and your WhatsApp Business Platform account.
4. Describe the exceptions: a date you cannot do, an enquiry with no images, somebody who will not change channel, a message out of hours.
5. Run it for a fortnight and count how many enquiries reached a confirmed order.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Getting the images onto the order

This is the part that actually matters, and it is where DM ordering fails most expensively.

Images sent in a conversation stay in the conversation, which means scrolling on the morning you are decorating.

Attach them to the order record when the brief is agreed, not later.

Name what each one is for — the tier design, the colour, the topper — since three references without labels is ambiguity.

Keep the final agreed version distinct from everything discussed, because customers send alternatives and change their minds.

A picture nobody can find is a specification you do not have, whatever channel it arrived on.

Moving the conversation

Move at the date question, which is the moment the enquiry becomes an order rather than a browse.

Give a reason — so the date, the images and the price stay together — which customers accept readily.

One tap, not a request to save a number.

Carry the images across rather than asking them to send everything again, which is the most irritating possible redirect.

Some will not move, and those should be handled where they are rather than lost.

Measure the drop-off, since a redirect losing a meaningful share is costing more than the tidiness is worth.

The saved-post problem

Customers send a post from your own feed and say "like this one".

Which one is not always clear, particularly if you make a lot of similar cakes.

Screenshot it into the order rather than relying on a link, since posts get archived and links break.

Ask what specifically they liked, because "like this one" usually means one element rather than the whole cake.

Say what will differ, since an exact repeat of a cake made two years ago is rarely possible.

Your own back catalogue is a sales tool, and making it searchable for yourself is worth an afternoon.

Running both without losing anybody

Instagram for discovery and the portfolio, answered by a person.

A clear route to order in the profile and in replies.

WhatsApp for the brief, the quote, the deposit and the collection details.

One order record, which is neither inbox.

Check message requests, which is where new customers land and where they are most often missed.

Do not run two half-systems, which is how a date gets promised twice.

Posting the finished cake

The last step of an order is frequently the first step of the next one, and it is the point where the two channels finally work together.

Photograph every cake before it leaves, which takes a minute and is the only chance you get.

Ask the customer for theirs too, since a cake at a real party photographs differently from one on your bench.

Get permission before posting, separately from them sending it, and record that you asked.

Do not post anything identifying — a child's name on a cake, a venue, a date — without thinking about it first.

Tag the occasion rather than the person, unless they have said you may.

Post it when it is relevant, not months later, since a Christmas cake in March does nothing for either of you.

Making it survive

Never leave an order only in a conversation, on either channel.

Attach images to the order at the point of agreement.

Answer Instagram requests, daily, since that folder is invisible otherwise.

Have cover for the account when you are away, which a personal account does not allow.

Report the outcome: enquiries by channel, moved, ordered, and lost in between.

Limits worth knowing about

Instagram reach is not yours and changes without notice.

Both platforms restrict automation of personal accounts, with different rules.

Moving channel loses some customers, which is a cost rather than an oversight.

Neither is an order system, and two inboxes is two problems.

An account problem on Instagram costs the portfolio, which for a cake maker is most of the business.

What to do first

Attach reference images to the order record at the moment the brief is agreed, wherever they arrived. It takes no new tooling, and it removes the failure that costs most on a baking morning — scrolling a conversation for a picture you half remember while the buttercream is going soft.

Two habits make the difference. Move the conversation at the date question rather than earlier or later, since that is when the enquiry becomes an order and the reason is one customers accept immediately. And check your Instagram message requests daily, because that folder is where new customers land and it is invisible unless you go looking.

Frequently asked questions

Should cake orders be taken in Instagram DMs?

Instagram carries the pictures, which is genuinely the hardest part of a cake specification. It carries none of the date, the payment, the order state or the record you work from on a baking morning.

What actually goes wrong with DM ordering?

Images stay in the conversation, so you are scrolling for a reference while decorating. There is no state, so a confirmed order and an unanswered enquiry look the same. And requests are filtered, so new customers sit unseen.

What is the single most valuable habit?

Attaching reference images to the order record when the brief is agreed, labelled with what each one is for. A picture nobody can find is a specification you do not have.

When should I move the conversation?

At the date question, which is the moment an enquiry becomes an order. Give the reason — keeping the date, images and price together — and carry the images across rather than asking them to resend.

What about customers who send a post from my own feed?

Screenshot it into the order rather than relying on a link, since posts get archived. Ask what specifically they liked, because "like this one" usually means one element, and say what will differ from a cake made two years ago.

Should my portfolio move to WhatsApp?

No. Instagram does discovery better than anything else available to a cake business, and replacing it is the mistake. Complement it instead.

Where do bakers lose the most enquiries?

The Instagram message requests folder, which is filtered and where new customers land specifically. Checking it daily costs nothing.

Is running both channels a problem?

Only if both hold order information. One order record, neither inbox — two half-systems is how a date ends up promised to two people.

Can I post a photo of a customer's cake?

Photograph it before it leaves, and ask before posting — separately from them sending you a picture, which is not consent to publish. Think about anything identifying on the cake itself, such as a child's name, before it goes out.

Whose photo is better, mine or the customer's?

Both, for different reasons. Yours is controlled and taken in good light; theirs shows the cake at a real occasion, which tends to carry more weight with people deciding.

Related reading

• Taking custom cake orders over WhatsApp
• Where cake enquiries die
• WhatsApp or Instagram DMs for salon bookings