search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
BRANDS


How is that information stored and served? CW: Any information that’s on, for example, a product page on the website - there is a sheet on a Google Drive with all the information on it, and there’ll be a link from the B2B platform to that sheet. The shops and the distributors have a direct link to all the copy that they must use for each product, along with barcodes, SKU numbers, package weights, and all of that kind of stuff. Important to state here is that everyone has the same amount of information, and it’s all taken from the same place. No one’s making their own copy up, and then getting the technical information wrong. One version of the truth. One location to find it. As you said, with the barcode searching, and things like that, it’s small things like keeping that information updated in the backend, so that everything is completely consistent, meaning anyone can search through the site, in whatever way that they desire. It’s super important.


So the information that sits within there is like a versioning system, how does that work? Is there somebody that owns keeping the information source up to date? AD: Our founder Nathan Hughes and I run the overall thought process, as well as the look and feel of the site. We have our bi-weekly meetings, almost looking for


36 | November 2024


problems with it, and when we find them, ways that we can solve those problems. I do all of the brand’s graphic design, and therefore any


page layout and visuals on that side. If there’s a new page that we need to do, or there’s an issue that needs to change on the visual side of things, I will redesign that. If it’s something simple, I can then code it from there. If it’s a more labour-intensive thing that gets passed


on to Tom (at Catalogue) who we use for our back-end development. If it’s administration, we’ve got Jon Hicken, who does all of the back-end administration on the website. He keeps product features updated, makes sure that the tags are in the right place, and makes sure photos are updated.


Can you give an example of troubleshooting, problem-solving, or rectifying an error? AD: Very recently, we noticed there was a difference between the information on a size guide and on our product design sheet. Here we have to re-check everything and make sure that it is consistent. In this instance, it turns out there was just a typo and it


ended up on the size guide. So then it was my job to redesign the size guide and Jon’s


job to upload it and put it in the right places. Everything else had the correct information so it wasn’t a big undertaking.


www.bikebiz.com


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68