Vehicle fulfillment [vehicle_fulfillment]

The vehicle fulfillment [vehicle_fulfillment] attribute is used to detail the method by which the vehicle will be delivered to the customer. This group attribute is used with the store code [store_code] sub-attribute for in store fulfillment. Store code [store_code] isn't required for online offers.

The vehicle fulfillment [vehicle_fulfillment] attribute can be repeated up to 3 times for each offer, allowing dealers to specify an option for each fulfillment type.

On this page


When to use

Required Required for each offer that has an option for a delivery through vehicle fulfillment.

This attribute uses the following sub-attributes:

  • Option [option] (Required)
    • Supported values: In store [in_store] and Online [online]

  • Store code [store_code] (Optional; Required for option = in_store )
    • Repeated field: Yes, up to 500

The option [option] sub-attribute uses the following supported values:

  • In store [in_store]
    • This value is for vehicles online that are currently available in a store. In store [in_store] value requires a list of one or more store code values.
  • Online [online]
    • This value is for vehicles available online to be delivered to the customer’s address.

Format

Follow these formatting guidelines to make sure Google understands the data you submit.

Learn when and how to Submit your product data in English.

Type Unicode characters (Recommended: ASCII only)
Repeated field Yes, up to 3 times, once per option type.
File format Example value
Type Unicode characters (Recommended: ASCII only)
Character limit

For store codes, 64.

For vehicle fulfillment, in store, up to 500 store codes are supported, delimited by a colon ( : ).

Text/Tab delimited in_store:1111
XML (Feeds)

<g:vehicle_fulfillment>

  <g:option>in_store</g:option>

  <g:store_code>1111</g:store_code>

</g:vehicle_fulfillment>

To format your data for Content API, go to the Vehicle ads Content API guidelines.


Minimum requirements

This is the requirement you must meet to show your product in Merchant Center. If you don't follow this requirement, we'll disapprove your product and notify you in your Merchant Center account. Follow these guidelines to make sure you submit high-quality data for your products.

  • If the method for vehicle fulfillment is the in store [in_store] attribute, then the store code [store_code] sub-attribute must also be submitted along with one or more appropriate store code values.
  • If you are specifying more than one store code value, then repeat :store_code in the header for each store code, up to the specified maximum.
Note: When using fewer store codes, the trailing ":" is still required for each store code mentioned in the header.

Best practices

These best practices can help you go beyond the basic requirements to optimize your product data for performance.

  • Either the vehicle_fulfillment attribute or the store code [store_code] attribute is required for in-store (local) ad targeting. It’s not required to provide both attributes.
  • If only a single store code will be associated with a given vehicle, the store code [store_code] attribute may be a simpler approach. View the “Vehicle fulfillment vs. store code” examples section below for illustration.

Examples

Submitting the vehicle_fulfillment group attribute

Group attribute vehicle_fulfillment
Sub-attributes
  • option
  • store_code

Text feeds

Format the group attribute name using vehicle_fulfillment, and then in parentheses, adding one of the supported fulfillment values followed by store_code (as needed). The store_code sub-attribute needs to be repeated for each store code value you want to submit, separated by a colon ( : ).

Example: In store fulfillment

If the store_code sub-attribute is repeated in the group attribute name, but only one store code value is submitted, the entry will still be accepted since there’s only one colon in the value.

When a colon ( : ) doesn't indicate a separate sub-attribute value, the value should be surrounded by quotes ( " ).

Name vehicle_fulfillment(option:store_code:store_code)
Values

in_store:1111:2222

in_store:1111

in_store:1111:”2222:2”

Example: Online fulfillment

The store_code sub-attribute isn't required for online offers.

Name vehicle_fulfillment(option)
Value online

Example: Hybrid offer

A hybrid offer combines both of the above examples as separate columns in the data.

{other feed cols} vehicle_fulfillment(option)

vehicle_fulfillment

(option:store_code:store_code)

... online in_store:1111:2222

Google Sheets

Format the group attribute name the same way as with text feeds. When a colon ( : ) isn't used to separate sub-attribute values, it should be submitted with a preceding backslash ( “ \ “ ).

Name vehicle_fulfillment(option:store_code:store_code)
Values

in_store:1111:2222

in_store:1111

in_store:1111:2222\:2

XML Feeds

Include the store_code sub-attribute as needed. To specify different fulfillment options, submit multiple vehicle_fulfillment attributes and include the store_code sub-attribute.

Example

<g:vehicle_fulfillment>
<g:option>online</g:option>
</g:vehicle_fulfillment>
<g:vehicle_fulfillment>
<g:option>in_store</g:option>
<g:store_code>1111</g:store_code>
<g:store_code>2222</g:store_code>
</g:vehicle_fulfillment>

Vehicle fulfillment vs. store code

The store_code attribute (feed top level) is equivalent to using vehicle_fulfillment with option = in-store. This is a simplified method of providing one or more store code values without the more complex structure of vehicle_fulfillment (option:store_code:...) group attribute.

For in-store, you must provide one or more store codes. With vehicle_fulfillment for in-store, note that the header in the feed (TSV or CSV file) must list a store_code header value for each store code in the vehicle offers.

Example

id ... vehicle_fulfillment(option:store_code:store_code:store_code) ... Comments
123 in-store:store1:store2:store3 3 store codes
456 in-store:store1:store2: 2 store codes and note the trailing colon required as a delimiter
789 in-store:store1:: 1 store code and note the trailing colons required as delimiters

All of the examples above can also be specified using only the store_code attribute because they’re only in-store (assuming a TSV or non-comma separated feed file in this example):

id ... store_code ... Comments
123 store1,store2,store3 3 store codes
456 store1,store2 2 store codes
789 store1 1 store code

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Google apps
Main menu
16573378254313870215
true
Search Help Center
false
true
true
true
true
true
71525
false
false
true
false