On this page
A national campaign with forty location accounts, published one account at a time, is forty chances to typo a caption, miss a location, or post at the wrong hour. Most multi-location teams that do it by hand budget a full day for what should take minutes.
Compose once, select every location
The bulk workflow is simple: write the post once, attach the creative, then select every connected location account that should carry it. One schedule step sends it everywhere. The campaign that took a day of copy-paste goes out in one pass, and every location publishes the same approved content at the same time.
When a location needs something different
Sometimes one market needs different copy, a different offer, or a different language. In that case, duplicate the post for that account and edit the copy before it goes into review. The bulk flow covers the campaign; per-location exceptions stay deliberate and visible rather than improvised.
Keep approval in the loop
Publishing to every location at once raises the stakes of a mistake, which is exactly why the bulk flow should run through the same approval queue as everything else. One reviewer sign-off covers the campaign before it fans out. Sked's multi-location workflow pairs bulk publishing with that approval step, so speed never comes at the cost of control.
Common questions
Good questions.
How many accounts can I publish the same post to at once?
You compose once, select every connected location account that should carry the post, and schedule. This works across the platforms Sked supports, so a national campaign goes out in one pass.
Can each location get a different version of the post?
Today the bulk flow publishes the same content to every account you select. If a location needs different copy, duplicate the post for that account and edit it before it goes into review.
