Sending a design to GFcrew

This tutorial walks you through sending a finished design to GFcrew so the photo appears on the storefront immediately and parents can purchase it right away.

Before you start

Your organization must have a GFIT key connected before GFcrew appears as a destination. If you haven't done that yet, see Connecting GFcrew and GFITpro (GFIT key setup). You also need a design open in Studio — GFcrew sends apply to designs, not to templates.

What event codes are and where they come from

Every GFcrew send requires two codes that tell GFcrew which storefront the photo belongs to:

Main Event Code — identifies the main event in GFcrew (for example, 1373).
Destination Event Code — identifies the sub-event or team within that event (for example, 042).

If your designs live in a Studio folder named with those codes — for example, a folder called 1373_MainEvent — Templified reads the code directly from the folder name and pre-fills it for you. You can also type or edit either code inline in the send dialog.

You don't have to repeat the code on every subfolder. To find the Main Event Code, Templified walks up the folder tree from wherever the design lives until it reaches the event folder named with the code. So a design nested inside a subfolder — a team folder, a Plaques or PDF subfolder, and so on — still inherits the correct Main Event Code from its parent event folder. A code saved directly on the design always takes priority over the folder name.

Send a design to GFcrew

The Send To panel in Studio with a GFcrew 'ADD to Event' destination and a design staged in the queue, ready for Send all

Sending through a Send-To preset is the standard approach. You can also use the design editor's export menu for a one-off send. Both paths are described below.

Using a preset (recommended)

Open your design in Studio. In the right panel, click the Send To tab.
Click the preset that includes your GFcrew destination. The design is staged in the queue.
If the design doesn't have event codes saved yet, an Add Event Codes dialog appears. Fill in the Main Event Code and Destination Event Code, then click Save & continue. Templified saves the codes on the design so you won't be asked again.
When you're ready to send, click Send all at the bottom of the Send To panel (or press Enter). Templified renders the design and delivers it to GFcrew.

The modal closes as soon as you confirm — the send runs in the background. A notification reports the outcome when it completes.

Using the export menu (one-off send)

Open the design in the editor. In the toolbar, open the export menu and choose Send to GFcrew.
In the Send to GFcrew dialog, verify or enter the Main Event Code and Destination Event Code.
Click Send. The dialog closes immediately — the render and upload continue in the background.

Photo goes live immediately

Templified tells GFcrew to activate the event and mark the photo as available the moment the render is delivered. Parents can view and purchase the photo right away — there is no additional publishing step required on the GFcrew side.

Tagging a photo to a player's roster

The Add Image to Roster checkbox and SMS message field inside the Send to GFcrew dialog

If you want GFcrew to text the player's family a quick-buy link the moment the photo uploads, check Add Image to Roster in the send dialog. This tags the photo to the design's player in GFcrew's roster.

When Add Image to Roster is on, an SMS message field appears. Edit the message text as needed — it must include the <url> token, which GFcrew replaces with that photo's direct purchase link. The message is capped at 300 characters (one SMS segment).

The key benefit: if the player's roster entry has a parent phone number on file, that parent is automatically texted a direct quick-buy link to their own child's photo — they tap the link and buy, with no need to search the storefront or find their player. If the roster entry has no phone number, the photo is still tagged to the player in the roster, but no text goes out.

Re-sending a design (replace or create new)

If you've fixed a typo or updated the photo and want to push a new version to GFcrew, open Send to GFcrew again. Because this design was already sent, GFcrew shows a choice:

The Replace in GFcrew? prompt asking whether to replace the existing copy with your updated version or keep it

Replace the existing copy in GFcrew — overwrites the photo in place. The GFcrew record keeps the same filename, so returning parents don't see a duplicate.
Create a new copy in GFcrew — adds a second record. Use this only when you genuinely want a separate listing.

For corrections (name spelling, jersey number, re-cropped photo), choose Replace the existing copy in GFcrew. The existing copy's order history is not affected.

Viewing send history

Every send to GFcrew — whether manual or triggered by automation — is recorded in the design's history. Hover over the history indicator on the design card in Studio to see a log of when the design was sent and to which destinations.