Two vendors on one store: split the work without breaking the checkout

Divide the actual surfaces, not just the job titles

Ask each vendor to list the templates, files, page assignments and settings its work would change. Compare the lists before either publishes. A design task can include the cart and checkout pages; a checkout task can include markup or styles in the same theme. Calling one vendor the designer and the other the payment specialist does not resolve that overlap.

For each overlap, choose one person to make the combined edit or put the edits in an explicit order. Record what the other vendor must preserve, the version both started from and the condition that would require a new agreement on scope. Work on separate surfaces can proceed independently only while those dependencies remain separate. A newly discovered shared template returns to the release queue rather than becoming an unrecorded exception.

Make the checkout type a shared decision

Record whether the assigned cart and checkout pages use WooCommerce blocks or classic shortcodes, along with the installed payment extension and version. WooCommerce documents that an incompatible gateway may not appear in the Checkout block. If only incompatible gateways are enabled, no payment method may be available. A visual checkout replacement can therefore alter payment availability without anyone deliberately changing the payment account.

WooCommerce's guidance on reverting to classic shortcodes applies to both cart and checkout. Treat a proposed switch as a paired change that both vendors can see. Before it reaches the release queue, require the checkout owner to identify the installed extension's compatibility evidence and the behaviors that must remain present. A designer's completed page and a specialist's completed settings are not enough if they describe different checkout types.

Use individual access without mistaking it for file ownership

WordPress documents theme switching and plugin activation as separate capabilities, but a single-site Administrator has both and can manage options and users. An Editor's default role does not include those installation capabilities. Choose access from the tasks each person must perform; do not label two Administrator accounts as isolated work areas. File and configuration ownership still needs the explicit agreement and release process above.

Where Stripe is the provider, its team feature provides individual invitations and roles, recommends the lowest permission needed, and logs team-member activity. Use those records to investigate payment-side changes, while recognizing that a Stripe activity log is not a history of WordPress theme edits. Other providers need their own access arrangements.

The shared release record must contain references to credentials' authorized custodians, never the credentials themselves. Stripe says secret and restricted API keys must not be shared over email, chat or other unencrypted channels. A request from the second vendor does not make forwarding a key an acceptable handoff.

Release against one current record

Keep one record that both vendors read before changing a shared surface. It should name the active versions, approved scope, queued work, current edit owner, release approver and last deployed change. Each vendor records its completed edit before handing the surface over. The next vendor compares its starting files and settings with that record; a stale full-site copy must not overwrite the other vendor's completed work or intervening order data.

Agree on the observations that would stop a release: a missing previously available payment method, a lost required checkout control or an unexplained order mismatch. Use actual rendered behavior and available real order records. If no order has exercised a changed path, record that limit; a page inspection alone cannot prove payment-to-order completion. Any reversal must account for subsequent changes and real orders rather than blindly restoring the earlier copy.

The merchant can now decide which changes may proceed independently and which need a coordinated handoff. For a Prism checkout consultation, describe the overlapping surface, the proposed sequence and the behavior at risk. Confirm the assistance, responsibilities, fees and terms before work. Coordinating vendors does not transfer the provider's authority over the research-only business's eligibility.

Vendor boundary map

Complete this jointly from the current store and the two real scopes of work. In the last column name the edit owner, other vendor's dependency, release order and evidence reference. An unassigned shared surface remains unresolved.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.