Instagram Automation for Clothing Brands

Generic keywords already live in SIZE, RESTOCK, and PRICE. This article is fashion-specific: fit language you can stand behind, drops, and returns copy. Drops: product drop playbook. Launches: product launches. Per-SKU keywords on the right media, size chart in the DM, humans for fit edge cases.

A denim Reel is not a candle shop. Inseams, rise, “runs small,” maternity, and fabric stretch are the comments you already get. Automate the chart. Do not automate a guarantee that a 36-week bump will love the high-rise. Do not keep sending a 404 after the SKU is gone.

Fit is a DM, not a public essay

Send the size chart for that garment in the DM. Do not write a public essay about inseams on the comment thread. Public one-liner: “sent the chart.” If the answer is the chart plus “this style runs small,” that can be a script you will keep true. Maternity, tailoring, or a photo they need you to judge stays human.

• SIZE: chart for this SKU, fabric notes you would print on the PDP (“rigid 14oz, expect 1% after wash” only if true).
• FIT: if you teach it, it must still be the chart plus one honest sentence — not “you will look like the reel.”
• RESTOCK / WAITLIST: live PDP or waitlist. Do not send a 404. Pause when the colourway is gone.
• PRICE: current PDP. Sale end-dates belong in a rule you will actually pause.

Per-SKU media scoping

The navy barrel-leg Reel should not send the chart for the ecru straight-leg. Scope the rule to that media. If you run one SIZE word across the grid, put a button list in the DM (“reply NAVY or ECRU”) only if you will branch on the reply — and unmatched replies must not loop the checkout URL. A second keyword per colour on dedicated Reels is often cleaner.

Drops: teach the word on the drop Reel only. When sizes sell out, edit the DM to waitlist or “size 28 gone, 30 still live” if that is true — not a generic cart link that 404s size 28. Launch week will queue; non-followers will sit in Requests. Caption those facts. Comment-to-DM paces; it does not restock cotton.

Returns and what not to promise in public

Do not promise a fit, a delivery date, or a returns outcome in the automated DM unless that sentence is true for this SKU today. Send the returns policy URL. “Will I get a refund if the waist is huge?” is a human if your policy has photo conditions. COD, customs, and “my cousin in another country” are not SIZE. Handoff.

Public comments should stay one line. Fit arguments in public train the wrong behaviour and invite pile-ons. If someone comments a body measurement, do not repeat it back publicly. Take it to DM as a person if you are willing to advise; otherwise send the chart only and say you do not guess bodies from a comment.

A denim drop, written as DMs

SIZE: “Here’s the chart for the navy barrel jean (SKU NVL-32). This pair runs small in the waist — most people size up one from our straight-leg. If you are pregnant, between sizes with a tailor, or sending a photo, reply HUMAN and we’ll read it. This chat will not guarantee a fit.” RESTOCK: “Navy 28 is on the waitlist form in this link. 30–34 are live on the PDP. I will not send a cart for 28 until it exists.” PRICE: “Current price is on the PDP. The weekend sale ends Sunday — I’ll pause this rule if the sale ends early.”

Handoff: alterations, wedding-week rush dye, wholesale. Wholesale should not share SIZE with DTC. Teach WHOLESALE on a B2B lookbook if you have MOQs, and keep those threads human after the line sheet.

Influencer codes on a garment Reel

If a creator posts your denim, their CODE rule is theirs (disclosure + their code). Your SIZE rule on your own repost still sends your chart. Do not merge the affiliate code into SIZE or you will leak a creator’s commission string on your grid. Attribution for house drops can use coupons as in the coupon article — still pause when the SKU dies.

What not to automate

Medical-adjacent comments (“this will fix my back”). You sell clothes. Send the chart or hand off. Do not claim compression or posture outcomes. Also: counterfeit reports, “you stole this design,” and chargebacks. Pause the SKU rule if you pulled the product for a defect — sending SIZE on a recalled batch is how you multiply returns.

Navy barrel chart on an ecru Reel is a return you scheduled

Scope SIZE to that garment’s media. Comment on the navy barrel Reel: “SIZE.” First DM: “Chart for the navy barrel jean (SKU NVL-32). This pair runs small in the waist — most people size up one from our straight-leg. Pregnant, between sizes with a tailor, or sending a photo: reply HUMAN. This chat will not guarantee a fit.” If that rule also sits on the ecru straight-leg Reel, you just mailed the wrong inseam. A button list (“reply NAVY or ECRU”) only if you will branch — unmatched must not loop the checkout URL.

Do not write a public essay about inseams on the comment thread. Public one-liner: “sent the chart.” If someone comments a body measurement, do not repeat it publicly. Take it to DM as a person if you will advise; otherwise send the chart only and say you do not guess bodies from a comment.

36-week bump, recall, wholesale — three exits that are not SIZE

Maternity and “will this fit a 36-week bump” are human if you cannot stand behind a sentence. Sending the PDP again is how you look automated and unsafe. Recall or defect: pause the SKU rule. Sending SIZE on a pulled batch multiplies returns. Medical-adjacent “this will fix my back”: you sell clothes. Chart or hand off. No compression or posture claims.

WHOLESALE on a B2B lookbook: line sheet, MOQs, then human. Do not share SIZE with DTC. Counterfeit reports and “you stole this design” are human. COD, customs, and “my cousin in another country” are not SIZE. Returns: send the policy URL. “Will I get a refund if the waist is huge?” is a human if your policy has photo conditions.

Drop week: size 28 gone, 30–34 live

RESTOCK first DM: “Navy 28 is on the waitlist form in this link. 30–34 are live on the PDP. I will not send a cart for 28 until it exists.” PRICE: “Current price is on the PDP. Weekend sale ends Sunday — I’ll pause this rule if the sale ends early.” Launch week will queue; non-followers sit in Requests. Caption those facts. CommentLink paces. It does not restock cotton. It does not populate a Shopify catalog in the DM. Paste the PDP you already have.

Influencer posts your denim: their CODE rule is theirs (disclosure + their code). Your SIZE rule on your repost still sends your chart. Do not merge the affiliate code into SIZE or you leak a creator’s commission string on your grid.

Fit copy you will print on the PDP or you do not automate it

• Rigid 14oz, expect about 1% after wash — only if true.
• Runs small in the waist versus the straight-leg — only if true this season.
• FIT as a second word still means the chart plus one honest sentence, not “you will look like the Reel.”
• Pause when the colourway is gone. A 404 cart is not RESTOCK.

A denim Reel is not a candle shop. Inseams, rise, maternity, and stretch are the comments you already get. Automate the chart. Do not automate a guarantee.

FAQ

How should clothing brands automate Instagram comments?

Per-SKU keywords on the right media, size chart in the DM, humans for fit edge cases.

Can SIZE be one rule for the whole grid?

Only if the DM can honestly ask which garment or you use one chart. Dedicated Reels per SKU are cleaner.

What about maternity or tailoring?

Human if you cannot stand behind a sentence. The chart can still go first.

Should RESTOCK send the PDP when the size is gone?

No. Waitlist or tell them which sizes are live. Do not 404 a cart.

Do I put the size chart on the public thread?

No. Send it in the DM. Public stays one line so the comments remain a community.

Is this the same as generic ecommerce keywords?

The words overlap. Fashion needs fit copy, SKU scoping, and returns honesty the generic list does not own.

Can one SIZE rule cover the whole grid if the DM asks which garment?

Only if you will branch on the reply and the else is not checkout. Dedicated Reels per SKU are cleaner.

They sent a photo of their bump. Send the size chart again?

Chart may already have gone. Next is HUMAN. Do not guarantee a 36-week fit in a loop.

Should we promise delivery dates in the AutoDM?

Only if that sentence is true for this SKU today. Otherwise policy URL or a human.

Related reading

• Ecommerce keywords
• Launches