Question 1

What is a durable workflow?

Accepted Answer

A workflow that runs for weeks and keeps its state the whole way. Each step records its result as it completes, so a failure or restart never loses progress. When a workflow pauses for an approval, it holds at that step and resumes from the same point once the decision comes in.

Question 2

Which templates are included?

Accepted Answer

Templates cover the multi-week projects most teams run. RFQ lifecycle runs from issuing the RFQ through collecting bids, scoring vendors, negotiating, awarding the PO, and receiving against the ASN. Seasonal demand prep forecasts the spike, identifies inventory gaps, and pre-positions stock. Carrier evaluation and switch benchmarks your current carriers, runs an RFP and a pilot, and migrates volume. Cost reduction campaign baselines spend, executes the opportunities, and measures the result. Supplier onboarding qualifies the vendor, sets up EDI, and ramps from a pilot PO to full volume. Every template is editable, and you can build your own from the same steps.

Question 3

How do AI agents fit into a workflow?

Accepted Answer

Agent steps dispatch work to the platform AI agents: scoring vendor bids, benchmarking carrier rates, drafting a negotiation position. Draft an agent, simulate it against your own data, then publish it before it takes a step. Each agent runs at the autonomy level you set, across six levels from manual to autonomous, and every action it takes is logged. You decide which decisions stay behind a human approval step.

Question 4

What happens when a workflow needs a decision from my team?

Accepted Answer

A human step creates an item in the approval queue, and a notification step can post to Slack or email. The workflow waits at that step until someone decides, then continues. Condition steps branch on the outcome, so an approval and a rejection can lead to different next steps.

Question 5

How are workflows different from automation rules?

Accepted Answer

A rule fires once when an event matches: set the trigger, add conditions with AND/OR logic and nested condition groups, pick the action, then rank execution order and validate it in test mode. A workflow runs for weeks across many steps and holds state between them. Recurring work runs on a cron schedule: a report, a data sync, or a maintenance job at the interval you set. Select carriers and generate labels with rules; run an RFQ or a carrier switch as a workflow; put the weekly report on a schedule. All three write every run to the execution log.

Question 6

What happens if a step fails?

Accepted Answer

The workflow keeps its state, and the failure shows in the execution log with what ran and where it stopped. Fix the cause and the workflow resumes from the failed step; completed steps hold their results. Timer steps and paused approvals survive restarts the same way.

Turn a repeatable process into a workflow

Workflows on CommerceShip

How a process becomes a workflow

Build the workflow

Test the workflow

Switch the workflow on

Watch the executions

Tell us which process you do manually

Workflow FAQs