You probably need to treat loyalty points as stock figures in inventory management, that you need to add to or subtract from as you see fit.  I would add a "loyalty point" field in your customer table, so each customer has a "loyalty point" number.  Add one to it when a customer places an order.  Deduct one from it when the customer (a) uses a loyalty point, if loyalty points are redeemable in some ways, or (b) cancels an order that is not the fault of the merchant.  If a customer buys an item and has to return it due to defects, resulting in a cancelled order, then obviously you don't want to deduct loyalty point from that.  If a customer receives your goods but delays in paying you, how do you deal with the loyalty point already given to the customer?  So there are business scenarios to consider as well as the technical aspect in Access.

Thank you, they receive a 10% discount off their order every time they accumulate 6 points, and I have yet to automate this part, payment is made on or before delivery of goods, if the order is not paid for and returned then they also receive no loyalty point for that order and the discount will be deducted from their next one so I'm guessing that would tie in with adding or deducting points.  I do have a loyalty point field in the customer table but have one in the order table that I have been using, i'm guessing I would need to increment using VBA.

I would consider giving loyalty points based on dollar value of an order (say, 1 point for every $1) instead of the number of orders.  You may not want a customer who placed a $10 order to receive the same points as one who placed a $1000 order.  This is, again, more of a business decision than a technical one.  The actual technical work of adding or subtracting points for a customer may be way simpler: you just look up a customer with an update query that also changes the point value for that customer.  E.g.:

    UPDATE CustomersT SET LoyaltyPts = LoyaltyPts + 1 WHERE CustomerID = 123;

Or LoyaltyPts - 1 for deducting a point.

In your table design, you want the loyalty point field to have a default value of zero, so newly-added customer will have a starting value of zero loyalty point.

You may also want to prevent subtraction from being done if the loyalty point is zero, so you won't get a negative value.  (Or maybe you do want negative values for this -- there might be a useful business purpose in that.)